Network Status
Real-time health of every system advertisers and publishers depend on, plus how we handle maintenance and incidents.
01 Components
Each component is probed every 30 seconds from monitoring nodes in Frankfurt, Ashburn, Singapore, and São Paulo. A component is marked degraded when error rate exceeds 1% or p95 latency exceeds twice its baseline for 5 consecutive minutes, and marked down when more than half of probes fail. Uptime figures cover the trailing 90 days.
02 Incident History
No incidents have been recorded in the trailing 90 days. When an incident occurs, it is listed here with its start time, affected components, severity, updates posted during the incident, and a post-incident review published within 5 business days of resolution. Post-incident reviews describe the cause, the customer impact, the fix, and the changes made to prevent recurrence.
Incidents older than 90 days are archived and available on request from support@d4rkw3b.network.
03 Maintenance Windows
Scheduled maintenance that could affect any customer-facing component is performed during the standing window of Tuesday 02:00 to 04:00 UTC. We announce maintenance at least 72 hours in advance on this page, on the status Telegram channel, and by email to account holders who have opted in to operational notices.
Ad serving, smartlink routing, click tracking, and postback ingestion are deployed with zero-downtime rollouts and are not taken offline for maintenance. Maintenance may briefly affect the dashboard, API, reporting freshness, and payment processing. Reporting delayed by maintenance is backfilled; no events are lost.
Emergency maintenance outside the standing window is performed only to address a security vulnerability or an active incident, and is announced as soon as the decision to proceed is made.
04 Incident Severity
| Level | Definition | Response | Update cadence |
|---|---|---|---|
| SEV-1 | Ad serving, smartlinks, or click tracking down or failing for more than 10% of requests; data loss affecting billing or payouts | Engineer engaged within 5 minutes, 24/7 | Every 30 minutes until resolved |
| SEV-2 | A core component degraded; postbacks delayed more than 15 minutes; dashboard or API unavailable | Engineer engaged within 15 minutes, 24/7 | Every 60 minutes until resolved |
| SEV-3 | Non-core component degraded; reporting delayed; a single region affected | Engineer engaged within 1 hour during business hours | At start, at resolution, and every 4 hours in between |
| SEV-4 | Cosmetic or isolated issue with a workaround available | Scheduled into the next release | At start and at resolution |
05 How We Communicate
- This page is updated first. The component list above reflects monitoring state automatically, and incident entries are written by the on-call engineer.
- Telegram: the status channel at t.me/d4rkw3b_status mirrors every status page update.
- Email: account holders who enable operational notices in dashboard settings receive SEV-1 and SEV-2 incident notifications and all maintenance announcements.
- Dashboard banner: active SEV-1 and SEV-2 incidents are shown at the top of every dashboard page.
- Account managers contact managed-service customers directly for any incident affecting their campaigns or zones.
We do not use vague language in incident updates. Each update states what is affected, what we know about the cause, what we are doing, and when the next update will be posted.
06 Availability Commitments
Our target monthly availability is 99.95% for ad serving, smartlink routing, click tracking, and postback ingestion, and 99.9% for the dashboard and API. Availability is measured as the percentage of one-minute intervals in the month during which the component served requests successfully from at least three of four monitoring regions, excluding announced maintenance windows.
Advertisers with a signed insertion order and publishers on managed service are eligible for service credits when monthly availability of ad serving or tracking falls below target: 5% of that month's spend or earnings for availability between 99.0% and 99.95%, and 10% below 99.0%. Credits are requested through your account manager within 30 days of the month end and are applied to the following month.
07 Subscribe to Updates
Choose any of the following:
- Join the Telegram status channel at t.me/d4rkw3b_status.
- Enable operational notices under Settings → Notifications in the dashboard.
- Poll the status endpoint at
https://api.d4rkw3b.network/v1/status, which returns the component list and state as JSON and requires no authentication.
To report a problem that is not shown here, email support@d4rkw3b.network with the affected component, your account ID, timestamps in UTC, and any request IDs or error messages. Reports from managed-service customers can also go directly to their account manager on Telegram.