Last checked: a minute ago
Get notified about any outages, downtime or incidents for Northpass and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Northpass.
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 NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Northpass App - AWS | Active |
Northpass App - Azure | Active |
Shopify API & Mobile | Active |
Communications | Active |
SendGrid API | Active |
SendGrid Event Webhook | Active |
SendGrid SMTP | Active |
Video | Active |
Wistia App | Active |
Wistia Embeds | Active |
Wistia Encoding | Active |
Wistia Stats | Active |
Wistia Uploads | Active |
View the latest incidents for Northpass and check for official updates:
Description: # Current Status Operational # Summary Yesterday morning \(EST time\), we deployed a platform enhancement meant to improve security and the process of customizing a school's look and feel. Specifically, we wanted to ensure customers have easy access to the latest jQuery libraries without having to directly reference the library in their templates. However, this caused issues for customers using our Learning Experience v2 \(LXv2\) who referenced jQuery 2.x in their school’s customization code. # Impact Any customer utilizing our LXv2 who referenced jQuery 2.x in their school’s customization code experienced an issue where learners were unable to access course content. # Root Cause Prior to version 3.x, the jQuery library did not include one of the methods that our LXv2 relies on. This resulted in our LXv2 throwing a JS error, which in turn blocked any learners from accessing course content. # Trigger We regularly and frequently deploy to our production instance, so this error was introduced in our deployment that occurred at 12:20 UTC or 8:20am EST. # Resolution We reverted our latest deployment to return the application to stability at 14:50UTC or 10:50am EST. We also plan to put additional logging and monitoring in place to detect these types of issues earlier. # Corrective Actions We’re putting additional logging and monitoring solutions in place to automatically detect javascript issues like this ahead of time. As we’ve reverted our deployment to resolve this issue, we will refrain from deploying these jQuery-specific changes for a time being \(until this is closely monitored\).
Status: Postmortem
Impact: Major | Started At: July 23, 2020, 12:30 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: July 10, 2020, 8:36 a.m.
Description: This incident has been resolved
Status: Resolved
Impact: None | Started At: May 25, 2020, 11:19 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 22, 2020, 1:08 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 19, 2020, 5:01 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.