Urlbox Outage History

Urlbox is up right now

Urlbox had 4 outages in the last 2 years totaling 3h 55m of downtime — averaging 0.2 incidents per month.

There were 4 Urlbox outages since April 19, 2026 totaling 3h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.urlbox.io

Minor June 2, 2026

Investigating reports of API errors and timeouts

Detected by Pingoru
Jun 02, 2026, 06:05 AM UTC
Resolved
Jun 02, 2026, 09:23 AM UTC
Duration
3h 18m
Timeline · 4 updates
  1. investigating Jun 02, 2026, 08:25 AM UTC

    Investigating reports of API errors and timeouts.

  2. identified Jun 02, 2026, 08:53 AM UTC

    The final step in our rendering pipeline was overwhelmed by a spike in complex requests from multiple users. This caused a dramatic increase in processing times and the backlog is still being processed.

  3. monitoring Jun 02, 2026, 09:03 AM UTC

    Additional API pods have been deployed to increase processing capacity and reduce the backlog. We are seeing gradual improvements in processing times and will continue monitoring until the system has fully recovered.

  4. resolved Jun 02, 2026, 09:30 AM UTC

    Additional API capacity was deployed to process the backlog. Queue lengths have returned to normal and all pending requests have been processed.

Read the full incident report →

Minor June 1, 2026

Investigating a major outage of our API

Detected by Pingoru
Jun 01, 2026, 02:03 PM UTC
Resolved
Jun 01, 2026, 02:25 PM UTC
Duration
22m
Timeline · 5 updates
  1. investigating Jun 01, 2026, 02:03 PM UTC

    We are investigating an outage that is impacting availability of our API and dashbaord.

  2. identified Jun 01, 2026, 02:24 PM UTC

    We have identified the cause of the current API disruption and have applied a capacity increase to the affected infrastructure. The update is currently in progress. We are monitoring recovery and will post another update as soon as services are confirmed healthy.

  3. monitoring Jun 01, 2026, 02:44 PM UTC

    A spike in API requests from multiple large customers resulted in our Redis datastore reaching its memory limit. This prevented API pods from starting correctly. We increased Redis capacity, the upgrade is now complete, and services are back online. We are continuing to monitor the platform closely and will review our processes to reduce the risk of this happening again.

  4. monitoring Jun 01, 2026, 03:13 PM UTC

    Around 500 thousand requests, including some from around 11am were delayed as a results of degraded performance in the run up to this incident. We are working through the backlog.

  5. resolved Jun 02, 2026, 12:16 AM UTC

Read the full incident report →

Minor April 30, 2026

Some GPU requests failing

Detected by Pingoru
Apr 30, 2026, 11:30 AM UTC
Resolved
Apr 30, 2026, 11:45 AM UTC
Duration
15m
Timeline · 1 update
  1. resolved Apr 30, 2026, 11:36 AM UTC

    Some GPU enabled requests were failing during this window. This has now been resolved.

Read the full incident report →