Urlbox Outage History

Urlbox is up right now

Pingoru has recorded 5 incidents for Urlbox: 5 in the last 12 months and 1 in the last 90 days.

Source: status.urlbox.io

5incidents recorded
5last 12 months
1last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Urlbox in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026219 of 720 (3%)
May 202600 of 744 (0%)
June 202624 of 720 (1%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202611 of 558 (0%)

Incidents, newest first

Major October 1, 2026 Major outage: render requests failing 38m

Started Oct 01, 2026, 09:33 AM UTC· resolved Oct 01, 2026, 10:11 AM UTC

  1. investigating Oct 01, 2026, 09:33 AM UTC

    Since 09:33 UTC, most new render requests (screenshots, PDFs and videos) are not completing and are timing out. Cached renders are still served. We have identified the cause in our job-queue infrastructure and are working with our provider to restore it. Webhook deliveries for affected renders will be delayed. We will post another update within 30 minutes.

  2. identified Oct 01, 2026, 10:12 AM UTC

    We are treating this as a major outage. Since 09:33 UTC our job-queue datastore, run by our managed hosting provider, has been accepting connections but not completing them, so new render requests cannot be processed and are timing out. Service has briefly recovered at times and then failed again. The problem is on our provider's side, and we have escalated it to them with high priority. Cached renders are still being served. Queued webhook deliveries will be sent once service is restored. Our next update will be within 30 minutes.

  3. monitoring Oct 01, 2026, 10:31 AM UTC

    Service has recovered. Our provider's job-queue datastore became reachable again, and from 10:11 UTC new render requests have been completing normally across all regions. All of our render monitors were passing again by 10:17 UTC. Jobs and webhook deliveries that were queued during the outage have been processed. Some requests made between 09:33 and 10:11 UTC timed out and may need to be retried. We are monitoring closely and will post a full summary once the incident is resolved.

  4. resolved Oct 01, 2026, 11:43 AM UTC

    Resolved. Render processing has been fully back to normal since 10:11 UTC and has stayed stable since. Between 09:33 and 10:11 UTC (about 38 minutes), the datastore behind our render job queues stopped responding, so new screenshot, PDF and video renders did not complete. Renders and webhooks queued during that window were all processed by 10:42 UTC. Synchronous requests made between 09:33 and 10:11 UTC may have timed out and can be retried. We have since added capacity and redundancy to that datastore. We are working with our provider to confirm the root cause, and will share what we are changing to prevent this happening again.

Read the full incident report →

Minor June 2, 2026 Investigating reports of API errors and timeouts 3h 18m

Started Jun 02, 2026, 06:05 AM UTC· resolved Jun 02, 2026, 09:23 AM UTC

  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 22m

Started Jun 01, 2026, 02:03 PM UTC· resolved Jun 01, 2026, 02:25 PM UTC

  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 15m

Started Apr 30, 2026, 11:30 AM UTC· resolved Apr 30, 2026, 11:45 AM UTC

  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 →

Major April 19, 2026 Major Outage detected on status page 18h 42m Overall

Started Apr 19, 2026, 08:49 PM UTC· resolved Apr 20, 2026, 03:31 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →