Adnuntius Outage History

Adnuntius is up right now

Adnuntius had 2 outages in the last 2 years totaling 3h 50m of downtime — averaging 0.1 incidents per month.

There were 2 Adnuntius outages since December 4, 2024 totaling 3h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.adnuntius.com

Notice July 14, 2025

Ad serving disrupted

Detected by Pingoru
Jul 14, 2025, 10:38 PM UTC
Resolved
Jul 14, 2025, 11:08 PM UTC
Duration
30m
Affected: Ad Serving
Timeline · 3 updates
  1. monitoring Jul 14, 2025, 10:38 PM UTC

    Ad requests are taking a long time to process and some may fail to return ads to the client browser due to the connection timing out. The source of this has been identified as a failure in DNS lookups that is caused by a CloudFlare outage (https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f). We have taken action to prevent these DNS timeouts from impacting the ad request processing. The CloudFlare issue has been identified and is being resolved by their engineers.

  2. monitoring Jul 14, 2025, 10:58 PM UTC

    Most ad request processing is back to normal now. We will continue to monitor this until the CloudFlare issue has been resolved.

  3. resolved Jul 14, 2025, 11:08 PM UTC

    The CloudFlare issue has been resolved (https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f). We will now undertake a review of our systems, and make changes to prevent a similar outage in an external system from impacting our ad delivery performance.

Read the full incident report →

Minor December 4, 2024

Delayed raw log availability

Detected by Pingoru
Dec 04, 2024, 05:42 AM UTC
Resolved
Dec 04, 2024, 09:02 AM UTC
Duration
3h 20m
Affected: Ad Server Logs
Timeline · 2 updates
  1. identified Dec 04, 2024, 05:42 AM UTC

    Due to the router upgrades that happened at our primary datacenter earlier today, the processing of our raw log data has been delayed by several hours. Statistics in the user interface and API are not affected.

  2. resolved Dec 04, 2024, 09:02 AM UTC

    This incident has been resolved.

Read the full incident report →