Identified - DNSWatch DNS reporting data is still 12+ hours delayed. Data is reliably being processed and saved.

At this point in time, we understand the cause of delay and are researching options to improve it.

All other DNSWatch services are operating normally. Customers are properly protected.
Dec 12, 15:50 EST
Investigating - Currently, DNSWatch DNS reporting data is 12+ hours delayed. Customers' most recent weekly report and homepage are impacted, as the data is not available to populate these reports.

At this point in time, no data has been lost. We are currently investigating the cause of this delay.

All other DNSWatch services are operating normally. Customers are properly protected.
Dec 5, 10:08 EST

About This Site

We continuously monitor the status of DNSWatch and all its related services. If there are any interruptions in service, a note will be posted here.

DNS ? Operational
90 days ago
100.0 % uptime
Today
DNS (US) Operational
90 days ago
100.0 % uptime
Today
DNS (EU) Operational
90 days ago
100.0 % uptime
Today
DNS (APAC/Tokyo) Operational
90 days ago
100.0 % uptime
Today
DNS (APAC/Sydney) Operational
90 days ago
100.0 % uptime
Today
GO Client API ? Operational
90 days ago
100.0 % uptime
Today
GO Client API (US) ? Operational
90 days ago
100.0 % uptime
Today
GO Client API (EU) ? Operational
90 days ago
100.0 % uptime
Today
GO Client API (APAC/Tokyo) ? Operational
90 days ago
100.0 % uptime
Today
GO Client API (APAC/Sydney) ? Operational
90 days ago
100.0 % uptime
Today
Dashboard ? Operational
90 days ago
99.97 % uptime
Today
Blackhole ? Operational
90 days ago
99.79 % uptime
Today
Content Filtering Operational
90 days ago
100.0 % uptime
Today
Firebox Registrations ? Operational
90 days ago
100.0 % uptime
Today
RPZ zone transfers Operational
90 days ago
100.0 % uptime
Today
Website ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
DNS mean response time (US)
Fetching
DNS mean response time (EU)
Fetching
DNS mean response time (APAC/Tokyo)
Fetching
DNS mean response time (APAC/Sydney)
Fetching
GO Client API (US) Mean Response Time
Fetching
GO Client API (EU) Mean Response Time ?
Fetching
GO Client API (APAC/Tokyo) Mean Response Time
Fetching
GO Client API (APAC/Sydney) Mean Response Time
Fetching
Dashboard mean response time
Fetching
Blackhole mean response time
Fetching
Past Incidents
Jan 29, 2020

No incidents reported today.

Jan 28, 2020

No incidents reported.

Jan 27, 2020

No incidents reported.

Jan 26, 2020

No incidents reported.

Jan 25, 2020

No incidents reported.

Jan 24, 2020

No incidents reported.

Jan 23, 2020

No incidents reported.

Jan 22, 2020

No incidents reported.

Jan 21, 2020

No incidents reported.

Jan 20, 2020

No incidents reported.

Jan 19, 2020

No incidents reported.

Jan 18, 2020

No incidents reported.

Jan 17, 2020

No incidents reported.

Jan 16, 2020
Resolved - An ad domain (agkn[.]com) was erroneously added to the DNSWatch blacklist which caused a spike in traffic to the blackhole. DNSWatch has finished procesing a backlog of alerts.

All systems are currently operational. DNSWatch continued to protect customers throughout this incident.
Jan 16, 17:23 EST
Investigating - We are currently investigating a very large spike in blocked traffic. This traffic is impacting the performance of the blackhole.

Customers visiting blocked domains may not see a block page.

We will update this issue as we continue to investigate.
Jan 16, 16:51 EST
Jan 15, 2020

No incidents reported.