Last checked
Delivery management platform for simplifying complex deliveries and optimizing last mile.
Experiencing an issue?
Czy Bringg nie działa?
Maintenance
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Bringg has active maintenance
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Unknown | ||
| 1h 20m | Yes | Major | ||
| 5h 23m | Yes | Major | ||
| 2h 40m | Yes | Minor | ||
| 56m | Yes | Major | ||
| 32m | Yes | Unknown | ||
| 1h 2m | Yes | Major | ||
| 1h 5m | Yes | Major |
Planned work published by the official provider.
Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade
Started 11 paź 2026, 07:00 UTC · Ongoing
We will be undergoing scheduled maintenance during this time.
Started 4 paź 2026, 05:00 UTC · Ongoing
Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade
Started 27 wrz 2026, 07:00 UTC · Ongoing
Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade
Started 13 wrz 2026, 07:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 23 sie 2026, 07:00 UTC · Resolved 23 sie 2026, 08:00 UTC
The scheduled maintenance has been completed.
Started 11 sie 2026, 03:00 UTC · Resolved 11 sie 2026, 03:10 UTC
The scheduled maintenance has been completed.
Started 5 lip 2026, 06:00 UTC · Resolved 5 lip 2026, 06:30 UTC
Hello 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 available. Thank you for your understanding.
Started 5 cze 2026, 06:00 UTC · Resolved 5 cze 2026, 06:30 UTC
Podziel się swoimi przemyśleniami na temat Bringg
Bądź pierwszą osobą, która skomentuje!
Uptimus monitoruje Bringg przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 70 komponentów, 53 incydentów, 57 konserwacji i 8 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Bringg. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Otrzymuj alerty, gdy Bringg lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 53 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „Degraded performance address geocoding”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 70 komponentów Bringg: Access / Authentication (EU2-GCP), Access / Authentication (US2-GCP), Access / Authentication (US3-GCP), Access / Authentication (US4-GCP). Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.
| Kryteria porównania | Uptimus | Downdetector |
|---|---|---|
| Zgłoszenia społeczności dotyczące Bringg |
The official status page for Bringg reports normal operation. 0 reports were recorded for Bringg in the last 24 hours. Last official check: .
| Dostępne |
| Dostępne |
| Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awarii | Dostępne | Dostępne |
|---|
| Aktywność z 24 godzin i regionalna mapa awarii | Dostępne | Dostępne |
|---|
| Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier Android | Dostępne | Oddzielny produkt |
|---|
| Alerty e-mail, push i webhook z tego samego obszaru | Dostępne | Oddzielny produkt |
|---|
| Oficjalne aktualizacje i historia statusu Bringg | Dostępne | Oparte na zgłoszeniach |
|---|
| Stan komponentów i prace serwisowe pokazane osobno | Dostępne | Ograniczone publicznie |
|---|
Rate this service
No reviews yet