Is there an Julota outage?
Julota status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Julota and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Julota and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Julota.
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 |
|---|---|
| Julota Platform | Active |
| Julota Reach | Active |
| www.julota.com | Active |
View the latest incidents for Julota and check for official updates:
Description: The incident has been resolved. Julota rotates SSL certificates annually to upgrade security to the latest, industry leading encryption. At approximately 1:25 pm MST, Julota's SSL certificate for "reach.julota.com" became expired and a new certificate was to be rotated into the platform. We have identified an error in our SSL certificate rotation that prevented the new certificate from being installed as expected, resulting in the existing SSL certificate for "reach.julota.com" remaining in effect, which shortly after expired. At approximately 2:20 pm MST, the new SSL certificate was successfully installed and revalidated by a Certificate Authority (CA), replacing the existing expired certificate. Please rest assured, all connections were still secure during this timeframe, ensuring all data was received and transmitted safely and securely using TLS v1.2 and AES-256 encryption. There was no gap in security nor lowered or missing encryption -- the Julota platform is not accessible without valid encryption in place. We will be updating our procedures to address the series of events that led to this predicament to ensure our SSL certificate rotation process does not experience a disruption like this in the future. We sincerely apologize for any inconvenience this may have caused. Some Users accessing Julota via a browser, such as Chrome, may have received a page showing the connection was not secure and were prevented from logging in. Some browsers may have shown a message similar to "Your connection is not private" and "Attackers might be trying to steal your information from reach.julota.com". Unfortunately, messages like this are very generic and can often lead to a misunderstanding of the actual issue. The issue was directly related to "ERR_CERT_DATE_INVALID", which is a message indicating the SSL certificate has passed it's validation date and had nothing to do with attackers or unencrypted connections. Normally, our SSL certificate rotation process prevents this from becoming an issue but the SSL certificate did not rotate as expected. Some Users may have also found a way around this issue by using a different browser or validating the connection themselves and were able to continue working per normal. Some Users that were already logged in were able to continue working as expected. Please reach out to your Julota representative if you have any questions or concerns.
Status: Resolved
Impact: Major | Started At: Sept. 19, 2023, 8:11 p.m.
Description: The issue with our upstream telecom carrier has been resolved. All failed faxes have been resent.
Status: Resolved
Impact: Minor | Started At: July 24, 2023, 9:37 p.m.
Description: All SMS/Text messages through all carriers seem to be fully operational. We will continue to monitor the incident while network maintenance for carriers are underway.
Status: Resolved
Impact: Minor | Started At: April 24, 2023, 3:10 p.m.
Description: Between the time of 08:22 am and 08:42 am MST on 03/22/2023, some Julota Users experienced an issue when trying to log in. Impacted Users would have seen an error stating “Cannot connect to server” when attempting to log or complete Multi-Factor Authentication message. Users may have seen this error but with multiple login attempts succeeded to log into Julota. This incident affected a small number of Julota Users during the incident timeframe. One of our authentication nodes became "unhealthy" and could not process login requests. The node was removed from our system and replaced with a "healthy" node that can successfully respond to login requests. We have identified a gap in our High Availability automation and testing coverage for our Authentication nodes and will be updating our automation and monitoring to cover address this gap. Normally, when a node is identified by the Julota platform as "unhealthy", the node is automatically replaced behind the scenes and the issue resolves itself within a few minutes. Due to that gap, the node was not marked as unhealthy and was not automatically replaced, but required manual replacement. The updates to the automation and monitoring that we are currently undergoing as high priority will help with prevention of issues like this and automatic replacement in the future. We apologize for this inconvenience and especially to the Users affected.
Status: Postmortem
Impact: Major | Started At: March 22, 2023, 2:22 p.m.
Description: Some of the instances on the Julota stack have been scheduled for retirement by AWS. Services will undergo a migration and restart onto new hardware. This process may cause up to 5 minutes of disruption in outbound internet connections originating from Julota. Services expected to be impacted or have a slight delay are: login tokens, notifications, alerts, automated reports, automated data extractions, and interfaces.
Status: Resolved
Impact: None | Started At: Feb. 27, 2023, 4 a.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.
