Is INVERS down?

Last checked 5m ago
Current status
INVERS is up

No incidents right now.

Official status page: https://status.invers.com · Polled every 5 minutes · 17 components tracked

INVERS is operational right now. Last checked 5m ago; the most recent incident resolved 5d ago.

Real-time INVERS status, recent outages, and incident history — pulled directly from INVERS's official status page at https://status.invers.com every 5 minutes. Pingoru tracks 17 INVERS services and has captured 30 incidents in the last 90 days (97.88% uptime). Get email, Slack, Discord, or webhook alerts the moment INVERS reports a new incident — free for 5 monitors, no credit card.

Users who monitor INVERS also follow these No-Code services: Zapier Airtable Webflow Typeform IFTTT Vasion Bubble Skylight Coda DoorDash View all 6,000+ providers
INVERS uptime 97.88% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 26m
    Started May 28, 2026, 08:46 AM UTC · Resolved May 28, 2026, 11:12 AM UTC
    CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    Timeline · 5 updates
    • investigating · May 28, 2026, 08:46 AM UTC

      We received reports of cellular connectivity issues. Our partner confirmed that there is an issue on some data sessions. The 24/7 teams of INVERS and the partner are working on it, we post new updates once available.

    • identified · May 28, 2026, 08:53 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · May 28, 2026, 08:56 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · May 28, 2026, 09:16 AM UTC

      The systems remain stable; if this continues, we will close the incident in about 30 minutes.

    • resolved · May 28, 2026, 11:12 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 13h 6m
    Started May 19, 2026, 06:55 PM UTC · Resolved May 20, 2026, 08:01 AM UTC
    CloudBoxx 1020 (LTE-M / 2G)CloudBoxx 4G (LTE / 2G)CloudBoxx 3G (3G / 2G)
    Timeline · 10 updates
    • investigating · May 19, 2026, 06:55 PM UTC

      We currently experience cellular connectivity issues. We are investigating.

    • investigating · May 19, 2026, 07:06 PM UTC

      We currently experience cellular connectivity issues with one of our providers. All CloudBoxxes connected via this provider are affected.

    • investigating · May 19, 2026, 07:25 PM UTC

      We are seeing improvements regarding the communication success rate. We will keep monitoring the connectivity metrics.

    • identified · May 19, 2026, 08:22 PM UTC

      Due to scheduled maintenance at a connectivity provider, all devices connected to that provider have been switched over to the alternative connectivity provider. There were brief interruptions during the switchover process. The situation has since stabilized, and the emergency teams and the connectivity team are working on the remaining unstable units.

    • identified · May 19, 2026, 08:52 PM UTC

      The situation regarding the remaining units continues to stabilize.

    • identified · May 19, 2026, 09:37 PM UTC

      It's taking longer for the remaining units to reconnect, but our teams are still on top of the situation

    • monitoring · May 19, 2026, 10:03 PM UTC

      The metrics are almost back to normal levels. The teams will continue to monitor the metrics and mark this incident as resolved if it remains stable over the next few hours.

    • monitoring · May 19, 2026, 10:05 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · May 20, 2026, 08:01 AM UTC

      This incident has been resolved.

    • postmortem · May 26, 2026, 07:38 AM UTC

      The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

    Latest: The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

  3. Resolved 26m
    Started May 12, 2026, 11:54 AM UTC · Resolved May 12, 2026, 12:20 PM UTC
    CloudBoxx REST API (Classic)OneAPI REST APISmartControl
    Timeline · 3 updates
    • investigating · May 12, 2026, 11:54 AM UTC

      Setups are currently not being processed

    • monitoring · May 12, 2026, 11:59 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · May 12, 2026, 12:20 PM UTC

      This incident has been resolved

    Latest: This incident has been resolved

  4. Resolved 31m
    Started Apr 14, 2026, 02:53 PM UTC · Resolved Apr 14, 2026, 03:24 PM UTC
    FleetControl
    Timeline · 2 updates
    • monitoring · Apr 14, 2026, 02:53 PM UTC

      We are experiencing an issue regarding event processing for FleetControl. For some vehicles the event log is not up-to-date and doesn't display the most recent events. We have identified the issue and implemented a fix. The event log is catching up.

    • resolved · Apr 14, 2026, 03:24 PM UTC

      Event processing is all caught up and the FleetControl event log displays the most recent events for all vehicles again.

    Latest: Event processing is all caught up and the FleetControl event log displays the most recent events for all vehicles again.

  5. Resolved 15m
    Started Mar 31, 2026, 08:16 AM UTC · Resolved Mar 31, 2026, 08:32 AM UTC
    CloudBoxx REST API (Classic)LoginFleetControlOneAPI REST APIOneAPI Event ConsumersCloudBoxx Events, Trackings, Heartbeats (Classic)SmartControlDamage Detection Activation/DeactivationService PartnersAnomaly Detection
    Timeline · 5 updates
    • investigating · Mar 31, 2026, 08:16 AM UTC

      We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

    • identified · Mar 31, 2026, 08:22 AM UTC

      RootCause has been identified. We are working on resolving the issue.

    • identified · Mar 31, 2026, 08:26 AM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Mar 31, 2026, 08:27 AM UTC

      Issue has been fixed. We are still monitoring the situation.

    • resolved · Mar 31, 2026, 08:32 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full INVERS outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse INVERS outage history →

Or sign up free to get alerts when INVERS breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →