Follow the recent outages and downtime for Onfleet iOS in the table below.
|
Start Time |
Type |
Length |
Message |
Details |
|||||
|---|---|---|---|---|---|---|---|---|---|
|
March 27, 2022 06:01 UTC |
MAINT |
about 3 hours |
Database upgrade |
See more
|
|||||
|
May 25, 2021 17:58 UTC |
WARN |
2 days |
Performance degradation |
See more
|
|||||
|
May 03, 2020 05:41 UTC |
MAINT |
about 2 hours |
High availability and disaster recovery improvements |
See more
|
|||||
|
April 26, 2020 05:36 UTC |
MAINT |
about 2 hours |
High availability and disaster recovery improvements |
See more
|
Onfleet iOS status, last 24 hours:
Up: 24 hours
Warn: 0 minutes
Down: 0 minutes
Maintenance: 0 minutes
We've been monitoring Onfleet iOS outages since April 25, 2020.
Here's the history of service outages we've observed from the Onfleet iOS Status Page:
Onfleet iOS is an eCommerce solution that StatusGator has been monitoring since April 2020. Over the past about 4 years, we have collected data on on more than 1,350 outages that affected Onfleet iOS users. When Onfleet iOS publishes downtime on their status page, they do so across 21 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
Many StatusGator users monitor Onfleet iOS to get notified when it's down, is under maintenance, or has an outage. We've sent more than 1,600 notifications to our users about Onfleet iOS incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If Onfleet iOS is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
Warn notifications are used when Onfleet iOS is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
Onfleet iOS posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Onfleet iOS enters a pre-planned maintenance window, keeping you up to date.
Since Onfleet iOS publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.
When Onfleet iOS posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When Onfleet iOS has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
Because Onfleet iOS has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
Are you experiencing issues with Onfleet iOS? Sign up to receive notifications when Onfleet iOS publishes outages.
Onfleet iOS Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of Onfleet iOS?
Sign up for StatusGator and see all historical information about Onfleet iOS outages and performance issues. Get free, instant notifications when Onfleet iOS goes down.
