Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Bringg

    Last checked 8 sept, 4:35 UTC

    Bringg status

    Delivery management platform for simplifying complex deliveries and optimizing last mile.

    Experiencing an issue?

    ¿Bringg no funciona?

    Maintenance

    The official status page for Bringg reports normal operation. 0 reports were recorded for Bringg in the last 24 hours. Last official check: 8 sept, 4:35 UTC.

    Source: official status page

    Having issues with Bringg?

    Share your experience to help others stay informed.

    OverviewActivityHistoryCommunityAbout

    Bringg service health graph

    Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.

    Bringg activity

    Loading reports… · Last 24 hours

    Download
    by Uptimus
    ————Now
    • No problems detected
    • Possible problems
    • Problems detected
    • Early warning
    • Official incident

    Small green bars: normal status (illustrative). Taller bars: report activity.

    Waiting for data

    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.

    View chart data
    15-minute report intervals · UTC
    StartEndReportsStatus

    Latest activity

    Last 24 hours

    1. Official status checked

      Bringg has active maintenance

      Official provider status
      8 sept, 4:35 UTC

    Bringg outage reports

    0 outage reports in the last 24 hours.

    No hay reportes recientes de interrupciones

    La comunidad no ha enviado reportes de interrupciones para este servicio en las últimas 24 horas.

    Recibe notificaciones cuando cambie el estado de Bringg

    Notificaciones por correo, push y webhook.

    Empezar a monitorizar

    Mapa de Interrupciones

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Ver mapa completo

    Mapa de Interrupciones

    Loading report locations…

    Bringg status history

    Official status observations, not measured service uptime.

    Last 60 daysDaily history
    Loading history…
    ——
    • Operativo
    • Problemas
    • Interrupción
    • Mantenimiento
    • Sin datos

    Bringg components

    Component nameStatus
    Bringg EU2-GCP — Access / Authentication (EU2-GCP) statusUp
    Bringg US2-GCP — Access / Authentication (US2-GCP) statusUp
    Bringg US3-GCP — Access / Authentication (US3-GCP) statusUp
    Bringg US4-GCP — Access / Authentication (US4-GCP) statusUp
    Bringg EU2-GCP — API / Integrations (EU2-GCP) statusUp
    Bringg US2-GCP — API / Integrations (US2-GCP) statusUp
    Bringg US3-GCP — API / Integrations (US3-GCP) statusUp
    Bringg US4-GCP — API / Integrations (US4-GCP) statusUp
    Bringg EU3-GCP — Access / Authentication (EU3-GCP) statusUp
    Bringg EU3-GCP — API / Integrations (EU3-GCP) statusUp

    Bringg incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved0m24 ago 202615:43 UTCYesUnknown
    Official status·Resolved1h 20m28 jun 202612:36 UTCYesMajor
    Official status·Resolved5h 23m23 jun 202616:41 UTCYesMajor
    Official status·Resolved2h 40m15 jun 202615:03 UTCYesMinor
    Official status·Resolved56m8 may 202612:17 UTCYesMajor
    Official status·Resolved32m5 may 202614:05 UTCYesUnknown
    Official status·Resolved1h 2m24 mar 202616:10 UTCYesMajor
    Official status·Resolved1h 5m16 dic 202519:45 UTCYesMajor

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Reporting Infrastructure Upgrade - US3

      Maintenance

      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 oct 2026, 07:00 UTC · Ongoing

    2. ✓

      Periodic upgrades for Bringg's server infrastructure - Sunday, October 4, 2026

      Maintenance

      We will be undergoing scheduled maintenance during this time.

      Started 4 oct 2026, 05:00 UTC · Ongoing

    3. ✓

      Reporting Infrastructure Upgrade - US2

      Maintenance

      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 sept 2026, 07:00 UTC · Ongoing

    4. ✓

      Reporting Infrastructure Upgrade - EU2

      Maintenance

      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 sept 2026, 07:00 UTC · Ongoing

    5. ✓

      Reporting Infrastructure Upgrade - EU3

      Resolved

      The scheduled maintenance has been completed.

      Started 23 ago 2026, 07:00 UTC · Resolved 23 ago 2026, 08:00 UTC

    6. ✓

      [US3] Preventive Maintenance - Message Queue Peak Load Readiness

      Resolved

      The scheduled maintenance has been completed.

      Started 11 ago 2026, 03:00 UTC · Resolved 11 ago 2026, 03:10 UTC

    7. ✓

      Scheduled Maintenance – Server Infrastructure Upgrade

      Resolved

      The scheduled maintenance has been completed.

      Started 5 jul 2026, 06:00 UTC · Resolved 5 jul 2026, 06:30 UTC

    8. ✓

      Scheduled Maintenance – Server Infrastructure Upgrade

      Resolved

      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 jun 2026, 06:00 UTC · Resolved 5 jun 2026, 06:30 UTC

    Discusión de la Comunidad

    Comparte tus pensamientos sobre Bringg

    A
    Aún no hay comentarios

    ¡Sé el primero en comentar!

    Acerca de la supervisión de Bringg en Uptimus

    Uptimus supervisa Bringg mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.

    Esta página incluye actualmente 70 componentes supervisados, 53 incidencias, 57 mantenimientos y 8 días de historial conocido.

    Uptimus es un servicio independiente y no está afiliado con Bringg. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.

    Cómo supervisa Uptimus Bringg

    Recibe alertas cuando Bringg o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 53 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Degraded performance address geocoding».

    Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 70 componentes de Bringg: Access / Authentication (EU2-GCP), Access / Authentication (US2-GCP), Access / Authentication (US3-GCP), Access / Authentication (US4-GCP). Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.

    Notificaciones de mantenimiento
    Recibe alertas cuando Bringg publica mantenimiento planificado, programado o activo. Uptimus ha indexado 57 ventanas de mantenimiento del historial disponible de Bringg. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Notificaciones de recuperación
    Entérate cuando Bringg o un componente afectado vuelve a funcionar correctamente. La página contiene 8 días de historial conocido y conserva los eventos resueltos para su revisión. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Mensajes de estado
    Uptimus conserva el título de la incidencia publicado por Bringg y lo muestra con el estado normalizado. El historial disponible contiene 53 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Degraded performance address geocoding».

    Preguntas Frecuentes

    Recibe notificaciones cuando cambie el estado de Bringg

    Empezar a monitorizar
    Similar services
    Comparison

    Uptimus vs Downdetector para Bringg

    Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.

    Uptimus vs Downdetector para Bringg
    Criterios de comparaciónUptimusDowndetector
    Reportes de la comunidad sobre Bringg
    Detalles del estado
    Las actualizaciones de incidencias y mantenimiento se conservan para seguir la investigación, mitigación y recuperación. Una actualización oficial reciente conservada por Uptimus dice: «Between 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 UTC. This entry has been published retrospectiv…».
    Filtrado de componentes
    Elige todos los componentes o solo los productos de Bringg que utilizas. Las alertas oficiales respetan esa selección. Uptimus supervisa actualmente 70 componentes de Bringg: Access / Authentication (EU2-GCP), Access / Authentication (US2-GCP), Access / Authentication (US3-GCP), Access / Authentication (US4-GCP). El filtrado modifica las alertas oficiales entregadas, pero no elimina los eventos del historial público.
    Incluido
    Incluido
    Línea base adaptativa que separa casos aislados de una interrupción ampliaIncluidoIncluido
    Actividad de reportes de 24 horas y vista regional de interrupcionesIncluidoIncluido
    Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos AndroidIncluidoProducto separado
    Alertas por correo, push y webhook desde el mismo espacioIncluidoProducto separado
    Actualizaciones oficiales de incidentes y cronología de BringgIncluidoBasado en reportes
    Salud de componentes y mantenimientos mostrados por separadoIncluidoLimitado en páginas públicas
    IncluidoBasado en reportes · Limitado en páginas públicasProducto separado

    Rate this service

    How would you rate Bringg over the last month?

    No reviews yet

    (Límite de una reseña por mes)

    Más servicios para monitorear

    Descubre otros servicios populares y su estado actual

    Ver todos los servicios
    BelongPath of Exile 2Chat AI: Ask Agent AnythingEpic Fantasy Color by NumbersSubscribe ProWebappioMyfitappSeismic SoftwareSendbird OregonProspectioPipedrive – Sales CRMJira Core