miLibris outages and incidents
Outage and incident data over the last 30 days for miLibris.
There have been 0 outages or incidents for miLibris in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowComponents and Services Monitored for miLibris
Outlogger tracks the status of these components for Xero:
API
Console
Content Delivery Network
Mindreader
| Component | Status |
|---|---|
| Publication | Active |
| Static | Active |
| API | Active |
| v3.x | Active |
| v4.x | Active |
| v5.x | Active |
| Console | Active |
| Console | Active |
| Multimedia Editor | Active |
| Push | Active |
| Content Delivery Network | Active |
| CA | Active |
| FR | Active |
| NL | Active |
| US | Active |
| Mindreader | Active |
| Push Notifications | Active |
Latest miLibris outages and incidents.
View the latest incidents for miLibris and check for official updates:
Outage on content delivery.
Description: We suffered a network outage this morning affecting several of our CDN servers. The problem is now resovled.
Status: Resolved
Impact: None | Started At: Aug. 16, 2018, 11:03 a.m.
Updates:
-
Time: Aug. 16, 2018, 11:03 a.m.Status: ResolvedUpdate: We suffered a network outage this morning affecting several of our CDN servers. The problem is now resovled.
CDN partial outage
Description: This incident is now resolved. The root cause is a limited network outage which affected several key components of our CDN servers.
Status: Resolved
Impact: None | Started At: July 5, 2018, 5:42 a.m.
Updates:
-
Time: July 5, 2018, 8:44 a.m.Status: ResolvedUpdate: This incident is now resolved. The root cause is a limited network outage which affected several key components of our CDN servers.
-
Time: July 5, 2018, 6:16 a.m.Status: MonitoringUpdate: We are continuing to monitor for any further issues.
-
Time: July 5, 2018, 6 a.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: July 5, 2018, 5:42 a.m.Status: InvestigatingUpdate: We are currently investigating this issue.
api shortage
Description: A faulty switch disrupted connections between our api server and our main message broker.
Status: Resolved
Impact: Major | Started At: April 8, 2018, 9:27 a.m.
Updates:
-
Time: April 8, 2018, 10:17 a.m.Status: ResolvedUpdate: A faulty switch disrupted connections between our api server and our main message broker.
-
Time: April 8, 2018, 9:27 a.m.Status: InvestigatingUpdate: We are experiencing a shorage on the core api, we are investigating.
Content delivery Issue
Description: We resolved a problem on our CDN stack occurring under very high load.
Status: Resolved
Impact: Minor | Started At: March 16, 2018, 7:47 a.m.
Updates:
-
Time: March 16, 2018, 9:29 a.m.Status: ResolvedUpdate: We resolved a problem on our CDN stack occurring under very high load.
-
Time: March 16, 2018, 7:47 a.m.Status: InvestigatingUpdate: We notice important trouble in content delivery in FR. Currently investigating.
API response time slowdown
Description: API core servers experienced a major slowdown when an external service failed. The incident occured between 8 and 9 am GMT +1
Status: Resolved
Impact: None | Started At: Feb. 11, 2018, noon
Updates:
-
Time: Feb. 11, 2018, 8:23 a.m.Status: ResolvedUpdate: API core servers experienced a major slowdown when an external service failed. The incident occured between 8 and 9 am GMT +1
