Major incident

Pulseway: Pulseway PSA - Unable to login

Oct 1, 2026, 15:13 UTC

started

17:12 UTC

resolved

1 h 59 min

duration

Affected: Pulseway PSA

Current status of Pulseway: Operational — live Pulseway status

Timeline

Oct 1, 2026, 15:13 UTC
investigating
We are aware of a problem where users are unable to login to Pulseway PSA and are getting a "Something went wrong, please try again." error. The Pulseway Engineering team is investigating the issue. Subscribe to the Pulseway status page for up-to-date information at https://status.pulseway.com/
Oct 1, 2026, 16:09 UTC
monitoring
A fix has been implemented and we are monitoring the results.
Oct 1, 2026, 17:12 UTC
resolved
This incident has been resolved.

Updates as published by Pulseway (original).

This was part of a wider event: 27 services reported incidents within the hour.

Clerk 16:10 UTC · Dashboard increased latency
Zoom 16:08 UTC · Service Degradation Affected Incoming and Outgoing Calls of Zoom Contact Center, Virtual Agents, Mail, Calendar, Meetings, Cloud Meeting Recordings, Webinars and Events
Moneris 16:07 UTC · Batch upload via SFTP - Important Update
SU ITS 16:06 UTC · Authentication Issues on vCenter
Constant Contact 16:03 UTC · Delays in email campaign sending
Aircall 16:02 UTC · Outbound calls from mobile Spanish numbers reaching an audio message.
Homebase 15:47 UTC · Service Disruption
MongoDB Cloud 15:41 UTC · Trigger processing may be delayed globally
Ably 15:36 UTC · Elevated API Errors
WorkOS 15:30 UTC · Elevated API and AuthKit errors for some requests (Columbus, OH region)
Wave 15:28 UTC · Latency across Wave
Red Hat 15:24 UTC · console.redhat.com Notifications - Emails Degraded
Ledger 15:23 UTC · Kaspa (KAS) Mainnet Degraded Service
Moveworks 15:20 UTC · Moveworks Assistant in Microsoft Teams Not Responding
namecom 15:20 UTC · Degraded Performance - .si Registry Connection