Occupancy Data Outage
Timeline · 1 update
- resolved May 11, 2026, 03:27 PM UTC
This incident has been resolved.
Butlr Outage History
Butlr is up right nowButlr had 19 outages in the last 2 years totaling 142h 39m of downtime, averaging 0.8 incidents per month.
There were 19 Butlr outages since April 9, 2025 totaling 142h 39m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Outage
Timeline · 1 update
- resolved Apr 02, 2026, 12:17 AM UTC
An internal processing service created unexpected load on our messaging infrastructure, which temporarily impacted the real-time delivery of sensor data.
Service Degradation
Affected: Other
Timeline · 4 updates
- investigating Nov 20, 2025, 06:24 PM UTC
We are currently investigating the issue.
- investigating Nov 20, 2025, 06:24 PM UTC
We are continuing to investigate this issue.
- investigating Nov 20, 2025, 06:30 PM UTC
We are continuing to investigate this issue.
- resolved Nov 20, 2025, 06:31 PM UTC
This incident has been resolved.
Algorithm Server Maintenance
Timeline · 1 update
- resolved Oct 16, 2025, 08:10 AM UTC
[Incident] Extended Algorithm Maintenance — Presence dashboards/APIs delayed Status: RESOLVED (Monitoring) Severity: Major | Regions: Global (impact primarily APAC, EMEA) | Components: Algorithm Server, Dashboard, Presence API Scheduled algorithm server maintenance intended for off-hours (EST) has been extended longer than expected, overlapping with APAC business hours. During this period, Presence dashboards and APIs showed delayed data refreshes. No data was lost; historical data will be fully backfilled.
3rd Party LTE Vendor (KORE) Connectivity Issues – Impacting Limited Devices in Japan and Australia
Affected: 3rd Party Vendor LTE Service
Timeline · 2 updates
- investigating Oct 07, 2025, 02:32 AM UTC
We are currently investigating degraded performance with our LTE vendor, KORE, which is affecting connectivity for approximately 5% of devices in Tokyo, Sydney, and Melbourne. Our team is actively working with the vendor to restore full service and will provide updates as more information becomes available.
- resolved Oct 07, 2025, 04:40 AM UTC
This incident has been resolved.
KORE CS0236081 - Maintenance Overrun - OmniSIM - 2025-09-16
Affected: 3rd Party Vendor LTE Service
Timeline · 2 updates
KORE Case CS0219698 - Service Degradation - KORE OmniSIM, eSIM Red and IOT eConnect - 2025-07-07
Timeline · 2 updates
- resolved Sep 11, 2025, 02:41 AM UTC
Impacted Services: Data When Start: Monday, July 07, 2025 12:38 UTC / Monday, July 07, 2025 08:38 EDT (UTC-4) End: Monday, July 07, 2025 16:15 UTC / Monday, July 07, 2025 12:15 EDT (UTC-4) What Description: Since 12:38 UTC, we are experiencing issues with data connectivity with one of our third party carriers in the Netherlands. Customers roaming in the Netherlands might experience a degradation on data services while establishing new sessions. Our carrier partner is working on identifying the root cause and to restore the impacted services as soon as possible.
- postmortem Sep 11, 2025, 02:42 AM UTC
**RESOLUTION :**Traffic on the Vodafone network in the Netherlands has returned to normal. The local operator is reporting a resolution on their issue. At this time, device behavior is expected to return to normal and no longer be impacted. We are resolving the incident at this time. **UPDATE 1 2025-07-07 15:26 UTC /2025-07-07 11:26 EDT \(UTC-4\)** : The root cause of the data connectivity issues has been identified by our third party carrier. Their engineers are currently working on restoring the services with high priority. At this moment, customers will still experience a degradation on data services whilst roaming under Vodafone Netherlands. Our teams are currently monitoring the situation. We will provide another update in 1 hour or sooner once more information becomes available.
KORE CS0219662 - Emergency Maintenance - KORE OmniSIM Reach, KORE eSIM, KORE GN, and IoT eConnect
Timeline · 1 update
- resolved Sep 11, 2025, 02:40 AM UTC
When Start: Thursday, July 10, 2025 08:30 UTC / Thursday, July 10, 2025 04:30 EDT (UTC-4) End: Thursday, July 10, 2025 10:30 UTC / Thursday, July 10, 2025 06:30 EDT (UTC-4) What Description: KORE will be performing an emergency maintenance for voice services for the above mentioned service types. During the maintenance, no service impact is expected. Our engineers will monitor the process closely to ensure the successful completion of this maintenance.
KORE Case CS0236589 - Service Degradation - OmniSIM US - 2025-09-09
Timeline · 2 updates
- resolved Sep 11, 2025, 02:13 AM UTC
Impacted Services: Provisioning Impacted Services: Network registration, data, SMS and voice When Start: Tuesday, September 09, 2025 17:00 UTC / Tuesday, September 09, 2025 13:00 EDT (UTC-4) End: Wednesday, September 10, 2025 15:22 UTC / Wednesday, September 10, 2025 11:22 EDT (UTC-4) What Description: An issue might be preventing newly activated OmniSIM US from registering to networks has been detected and is being investigated. We strongly recommend not to activate new OmniSIM US physical SIMs or OmniSIM US profiles until the investigation is complete. Further updates will be shared as they become available. Resolution: Our engineering team worked closely with our vendor to identify and resolve an issue that may have prevented newly activated OmniSIM US and Reach SIMs from connecting to mobile networks. The service degradation is now resolved.
- postmortem Sep 11, 2025, 02:13 AM UTC
Only impacted newly registered users. No impact to Butlr.
KORE Case CS0236562 - Service Degradation - OmniSIM - 2025-09-08
Timeline · 2 updates
- resolved Sep 11, 2025, 02:11 AM UTC
When Start: Monday, September 08, 2025 16:52 UTC / Monday, September 08, 2025 12:52 EDT (UTC-4) End: Monday, September 08, 2025 19:21 UTC / Monday, September 08, 2025 15:21 EDT (UTC-4) What Description: Engineers are currently investigating intermittent provisioning failures that has triggered one of our alarms. Investigations are currently underway and we will post an update with more detail shortly.
- postmortem Sep 11, 2025, 02:16 AM UTC
Resolution: Since 19:21 UTC, the provisioning issue has been resolved. KORE engineers have confirmed that the backlog of pending requests in the queue has been processed successfully. We are currently observing stability since our recovery, and no further disruptions have been observed. While some users may still experience minor latency, this is expected to resolve as services normalize. Our engineers will continue to monitor performance closely to ensure stability. No further updates are expected and the incident is now closed as resolved. Update 1 - 2025-09-08 18:00 UTC / 2025-09-08 14:00 EDT \(UTC-4\): KORE Engineers continue to work to resolve the issue. Backlog of the pending Requests in the queue has been processed and completed. A fix is expected in the coming 12 hours. Some minor issues or delays may occur until the fix is delivered. Engineers continue to monitor the situation closely. We will provide another update in 2 hours, or sooner if new information becomes available
KORE Case CS0235025 - Service Degradation - OmniSIM - 2025-08-31
Timeline · 2 updates
- resolved Sep 02, 2025, 12:44 AM UTC
Event: 3rd Party Vendor Scheduled Maintenance Impact: Degraded Kore SIM LTE service in APAC; Cellular Hive data impacted for approximately three hours from 04:06 UTC Impacted Services: Data When Start: Sunday, August 31, 2025 00:16 UTC / Saturday, August 30, 2025 20:16 EDT(UTC-4) End: Sunday, August 31, 2025 02:20 UTC / Saturday, August 30, 2025 22:20 EDT(UTC-4) What Description: As of 00:16 UTC, a data service degradation is impacting new network registrations of OmniSIM Reach,OmniSIM Rush and OmniSIM US service types. KORE Engineers are actively engaged and investigating the issue with high priority to restore normal functionality as soon as possible. Further updates will be shared as the situation develops.
- postmortem Sep 11, 2025, 02:15 AM UTC
**RESOLUTION**: We identified an issue with one of our Radius servers and have successfully resolved it. All services have been fully restored and are operating normally.
KORE Service Degradation Omni SIM 08-28-2025
Timeline · 2 updates
- resolved Sep 11, 2025, 02:19 AM UTC
Impacted Services: Voice, SMS, Data When Start: Thursday, August 28, 2025 07:38 UTC / Thursday, August 28, 2025, 2025 03:38 EDT (UTC-4) End: Thursday, August 28, 2025 09:29 UTC / Thursday, August 28, 2025, 2025 05:29 EDT (UTC-4) What Description: Since 07:38 UT our engineers have detected a service degradation affecting OMNI SIM Reach, Rush and KORE ESIM service types affecting Voice, Data and SMS. Our engineers are actively investigating the issue and will provide another update within 1 hour.
- postmortem Sep 11, 2025, 02:19 AM UTC
**UPDATE 1 2025-08-28 08:45 UTC / 2025-08-28 04:45 EDT \(UTC-4\)** : Our engineers observed a 50% drop in sessions on OmniSIM, with smaller declines across other impacted products. All APNs appear to be affected. We are continuing to monitor the situation closely, and signs of recovery are beginning to emerge. **RESOLUTION**: Our engineers have observed a recovery in session activity across affected services. The issue appears to be resolved, and systems are stabilizing. We will continue to monitor closely to ensure full restoration and maintain performance. \*\* BUTLR SERVICES IMPACTED IN APAC REGION.
KORE CS0232229 - Planned Maintenance - KORE OmniSIM - 2025-08-26
Timeline · 1 update
- resolved Sep 11, 2025, 02:24 AM UTC
Impacted Services: Data When Start: Tuesday, August 26, 2025, 07:00 UTC / Tuesday, August 26, 2025, 03:00 EDT (UTC-4) End: Tuesday, August 26, 2025, 10:00 UTC / Tuesday, August 26, 2025, 06:00 EDT (UTC-4) What Description: KORE will be performing a planned maintenance that will impact data services for the above mentioned solutions. During this maintenance, devices will be impacted as active data sessions will be disconnected, requiring devices to establish new data sessions. KORE engineers will be monitoring the process closely to ensure successful completion.
Webhook - Delivery Experiencing Issues
Affected: Webhooks
Timeline · 2 updates
- investigating Aug 19, 2025, 04:30 PM UTC
We are currently experiencing an issue impacting delivery of webhook events. The root cause has been identified as an internal server error affecting our webhook infrastructure. Our engineering team is actively working to implement a fix. We'll provide another update as soon as service is restored or we have a timeline for resolution. Please note: This issue is limited to webhook delivery. All sensors continue to function as expected, and no data has been lost. Thank you for your patience while we work to resolve this.
- resolved Aug 19, 2025, 05:28 PM UTC
This incident has been resolved.
KORE CS0228201 - Planned Maintenance - KORE GN, KORE eSIM, IoT eConnect, OmniSIM - 2025-08-05
Timeline · 1 update
- resolved Sep 11, 2025, 02:32 AM UTC
When Start: Monday, August 4, 2025 22:00 UTC / Monday, August 4, 2025 18:00 EDT (UTC-4) End: Tuesday, August 5, 2025 02:00 UTC / Monday, August 4, 2025 22:00 EDT (UTC-4) What Description: KORE will be performing a planned maintenance for the above mentioned service types. During the maintenance, no impact is expected as traffic will flow over redundant links. KORE engineers will closely monitor the maintenance to ensure successful completion.
KORE CS0224843 - Planned Maintenance - OmniSIM - 2025-07-30
Timeline · 1 update
- resolved Sep 11, 2025, 02:33 AM UTC
When Start: Wednesday, July 30, 2025 04:00 UTC / Wednesday, July 30, 2025 00:00 EDT (UTC-4) End: Wednesday, July 30, 2025 06:00 UTC / Wednesday, July 30, 2025 02:00 EDT (UTC-4) What Description: KORE will conduct a planned maintenance that will impact OmniSIM data services. During the maintenance window, active data sessions will disconnect, requiring devices to establish new data sessions. Devices are expected to reconnect immediately. KORE engineers will closely monitor the maintenance to ensure its successful completion.
KORE Case CS0227324 - Service Degradation - SuperSIM, OmniSIM, KORE eSIM, IoT eConnect - 2025-07-28
Timeline · 2 updates
KORE CS0224516 - Planned Maintenance - OmniSIM Reach, eSim, KGN, IOT eConnect - 2025-07-24
Timeline · 1 update
- resolved Sep 11, 2025, 02:39 AM UTC
When Start: Thursday, July 24, 2025 01:00 UTC / Wednesday, July 23, 2025 21:00 EDT (UTC-4) End: Thursday, July 24, 2025 03:00 UTC / Wednesday, July 23, 2025 23:00 EDT (UTC-4) What Description: During the maintenance window, ongoing voice calls will be dropped but reattempts should be successful due to redundant network elements. KORE engineers will closely monitor the maintenance to ensure successful completion.
API and Web Application Outage
Affected: M2M TokensButlr Dashboard
Timeline · 4 updates
- investigating Apr 09, 2025, 02:57 PM UTC
Incident: API and Web Application Outage Status: Investigating Impact: Users may be unable to access the API and web application. We are currently experiencing a system outage affecting both our API and web platform. Our engineering team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide an update every 30 minutes until the issue is resolved. Thank you for your patience and understanding.
- identified Apr 09, 2025, 03:12 PM UTC
We have identified the cause of the outage: a rate-limiting issue from a third-party service provider is currently impacting system performance. Our team is actively working with the provider to resolve the issue and restore full functionality as quickly as possible. We will continue to provide updates every 30 minutes until the issue is fully resolved. Thank you for your continued patience.
- monitoring Apr 09, 2025, 04:22 PM UTC
Incident: API and Web Application Outage Status: Monitoring Impact: Resolved The issue has been identified and resolved — service has been fully restored across both the API and web application. The root cause was a rate-limiting issue with a third-party service provider, which has since been addressed. Please note: all sensors continued to capture data during the downtime, and no data was lost. We are actively monitoring system performance to ensure continued stability. Thank you for your patience and understanding as we worked to resolve this issue.
- resolved Apr 09, 2025, 06:25 PM UTC
This incident has been resolved.