Is Sign In Scheduling Down?

PulsAPI checks Sign In Scheduling every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Sign In Scheduling status feed and refreshes automatically, so you are not looking at a stale cached answer.

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Sign In Scheduling recovers.

PulsAPI tracks Sign In Scheduling uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Sign In Scheduling.

PulsAPI polls the official Sign In Scheduling status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Yes. PulsAPI monitors 13 individual Sign In Scheduling components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Yes. Create a PulsAPI account and subscribe to Sign In Scheduling. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Sign In Scheduling status changes.

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Sign In Scheduling problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Sign In Scheduling alongside up to 9 other services at pulsapi.com/signup.