Partially Degraded Service
Functions Operational
90 days ago
99.98 % uptime
Today
America Degraded Performance
90 days ago
99.98 % uptime
Today
Login Apps Toronto ? Operational
90 days ago
99.98 % uptime
Today
HTTP Post Toronto ? Operational
90 days ago
99.97 % uptime
Today
TCP Toronto ? Operational
90 days ago
99.99 % uptime
Today
MQTT Publish Toronto ? Operational
90 days ago
99.95 % uptime
Today
MQTT Subscribe Toronto ? Operational
90 days ago
99.98 % uptime
Today
Events Engine Toronto ? Degraded Performance
90 days ago
99.98 % uptime
Today
Oceania Degraded Performance
90 days ago
99.98 % uptime
Today
Login Apps Sydney ? Operational
90 days ago
99.99 % uptime
Today
MQTT Publish Sydney ? Operational
90 days ago
99.95 % uptime
Today
TCP Sydney ? Operational
90 days ago
99.99 % uptime
Today
Events Engine Sydney ? Degraded Performance
90 days ago
99.99 % uptime
Today
SMS ? Operational
Twilio REST API Operational
Twilio SMS, Latin America Operational
Twilio SMS, Europe Operational
Voice ? Operational
Twilio TwiML Operational
Twilio Voice, Latin America Operational
Twilio Voice, Europe Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
REST API
Fetching
Past Incidents
Jan 22, 2020

No incidents reported today.

Jan 21, 2020

No incidents reported.

Jan 20, 2020

No incidents reported.

Jan 19, 2020
Resolved - This incident has been resolved.
Jan 19, 14:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 19, 03:47 UTC
Investigating - We have identified an error with the end-user app web portal access engine and are currently looking into the issue.
Jan 19, 03:07 UTC
Jan 18, 2020

No incidents reported.

Jan 17, 2020

No incidents reported.

Jan 16, 2020

No incidents reported.

Jan 15, 2020
Resolved - This incident has been resolved.
Jan 15, 20:20 UTC
Monitoring - We have released a hot patch with more Telegram instances and numbers for sending messages to avoid the throttling at Telegram's side. The alerts should be now working properly
Jan 14, 15:30 UTC
Identified - We have identified an issue related with the events engine and Telegram during the last hours. Ubidots sends alerts using the allowed methods from Telegram REST API, and actually, the service is rejecting external requests due to what we suspect is a throttling not at Ubidots side but at Telegram. Because of this, even if the alert is triggered by our events engine, it is not being processed and sent by Telegram.

We are working in a way to to avoid this throttling, but as it is something related with a third party, we do not have an ETA to solve it.
Jan 13, 21:01 UTC
Jan 14, 2020
Resolved - This incident has been resolved.
Jan 14, 16:46 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 14, 10:50 UTC
Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.
Jan 14, 10:40 UTC
Resolved - This incident has been resolved.
Jan 14, 01:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 14, 00:16 UTC
Investigating - We have identified an error with the end-user app web portal access engine and are currently looking into the issue.
Jan 14, 00:01 UTC
Jan 12, 2020

No incidents reported.

Jan 11, 2020

No incidents reported.

Jan 10, 2020

No incidents reported.

Jan 9, 2020

No incidents reported.

Jan 8, 2020

No incidents reported.