Bringg Outage History

26 incidents recorded over the last 365 days, 15 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bringg status100.00% uptime history

Every Recorded Bringg Incident

Bringg incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026Route Optimization delays and failuresThis incident has been resolved.12h 6mResolved
Oct 13, 2026SMS Service failing with timeout on EU3This incident has been resolved.3h 6mResolved
Oct 11, 2026Reporting Infrastructure Upgrade - US3The scheduled maintenance has been completed.1h 0mScheduled
Oct 4, 2026Periodic upgrades for Bringg's server infrastructure - Sunday, October 4, 2026The scheduled maintenance has been completed.4h 0mScheduled
Sep 27, 2026Reporting Infrastructure Upgrade - US2The scheduled maintenance has been completed.1h 0mScheduled
Sep 22, 2026Degraded API response time and optimization performanceThe incident has been resolved.1h 57mResolved
Sep 15, 2026Delayed email verification codesThis incident has been resolved.5h 40mResolved
Sep 13, 2026Reporting Infrastructure Upgrade - EU2The scheduled maintenance has been completed.1h 0mScheduled
Aug 24, 2026Degraded performance address geocodingBetween 12:42 UTC and 14:15 UTC on 24 August 2026, a portion of address geocoding requests failed to complete within the expected time and returned timeout errors. Service returned to normal operation at 14:15…0 minResolved
Aug 23, 2026Reporting Infrastructure Upgrade - EU3The scheduled maintenance has been completed.1h 0mScheduled
Aug 11, 2026[US3] Preventive Maintenance - Message Queue Peak Load ReadinessThe scheduled maintenance has been completed.1h 10mScheduled
Jul 5, 2026Scheduled Maintenance – Server Infrastructure UpgradeThe scheduled maintenance has been completed.30 minScheduled
Jun 28, 2026Quotes service - Degraded PerformanceThis incident has been resolved.1h 20mResolved
Jun 23, 2026Optimization Services — Degraded PerformanceThis incident has been resolved5h 22mResolved
Jun 15, 2026API Slowness on US2The incident has been resolved.2h 39mResolved
Jun 5, 2026Scheduled Maintenance – Server Infrastructure UpgradeHello everyone, Please note that the planned maintenance has been cancelled due to internal reasons and has been postponed to a later date. We will share an updated schedule and further details once they become…30 minScheduled
May 8, 2026OTP Code not being send to users during loginThe issue has been resolved.56 minResolved
May 5, 2026Bringg UI issueThe issue has been resolved.31 minResolved
Mar 24, 2026Partners integration service is downThe incident has been resolved.1h 2mResolved
Mar 22, 2026Scheduled Maintenance – Server Infrastructure UpgradeThe scheduled maintenance has been completed.4h 0mScheduled
Feb 1, 2026Scheduled Maintenance – Server Infrastructure UpgradeThe scheduled maintenance has been completed.4h 0mScheduled
Dec 16, 2025Roadie is experiencing a core platform outageThis incident has been resolved.1h 4mResolved
Dec 5, 2025DoorDash is experiencing service degradation due to a Cloudflare outageThis incident has been resolved.26 minResolved
Nov 24, 2025[EU3] Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 18, 2025An outage with the Uber APIThe Uber team has resolved the service interruption. The system is functioning normally.2h 32mResolved
Nov 9, 2025Web application and driver app login issuesThis incident has been resolved.41 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Bringg incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Bringg Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bringg acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Bringg outage in this window ran 12h 6m, against a mean recovery of 2h 15m. If you depend on Bringg in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.