We have finished monitoring the incident and all systems are operational, thank you for your patience and understanding.
We have fully identified the issue and all connectivity has been re-estabilished. After running our security scans for our yearly PCI audit we've upgraded a few packages that were outdated and tightened up a couple security parameters which made our servers to lose communication with our internal authentication APIs. This caused all servers to return HTTP 521 status codes for around 5 hours during the EST/PST dawn and early morning. All connectivity has been restored and this should be fully mitigated now. Our security and devops team will keep monitoring the servers for the next two hours and will close up this incident shortly.
We have identified that a recent improvement on our security stack caused connections to all of our APIs to time out and/or return a 521 status. We apologize for the inconvenience and will be disclosing more details shortly.
Have you ever missed an important outage from a third-party service? We've built IsDown, so you never miss another outage again. It's the easiest way to monitor all your SaaS and cloud providers and get alerted when an outage impacts your business.Start free trial
No credit card required · Cancel anytime · 2024 services available
Quickly identify external outages that impact your business. We are monitoring more than 2000 services in real time.
Birds-eye view over all your services statuses
Check the status page aggregated of all your services in one place. No more going to each of the status pages and managing them individually.
Outage monitoring in real time
We monitor 24 hours a day, 7 days a week and will notify you if there is an incident. No more wasting time trying to figure out why something isn't working.
Alerts in your favorite channels
Get instant notifications in your email, Slack, Teams, or Discord when we detect a service outage. Outage monitoring where you are already doing your work.
Easily integrate with your current tools and workflows
Using Zapier or Webhooks, you can easily integrate notifications into your processes. PagerDuty integration is also available.
Avoid notifications clutter
Configure which notifications you want to receive from each service. Filter notifications by service components. You can opt to receive notifications only when a specific component is affected. You can also choose to receive notifications with a certain severity.
Have multiple dashboards. Easily shareable with the world.
Create one dashboard for each of your teams/clients/projects. Monitor only the services that each uses. Dedicated dashboard with custom notification settings. Easily make your dashboard public and share it with the world.
Prepare for scheduled maintenances
Never again be caught off guard by unexpected maintenance from your services. A feed of the next scheduled maintenances is available.
Weekly Digest of the services' outages
Every Monday, you'll receive a weekly summary of what happened the previous week as well as the maintenance schedule for the following week.
DevOps & On-Call Teams
You already monitor your internal systems. What about the external services? Monitor the services your business depends on. Don't waste time looking elsewhere when external outages are the cause of issues.
IT Support Teams
Detect external outages before your clients tell you. Anticipate possible issues and make the necessary arrangements. Having proactive communication, builds trust over clients and prevents flow of support tickets.
5 minute setup,
instant value for your team
Start with a trial account that will allow you to try and monitor up to 40 services for 14 days.
There are 2024 services to choose from and you can start monitoring, and we're adding more every week.
You can get notifications by email, Slack, and Discord. You can also use Zapier or Webhooks to build your workflows.
You'll start getting alerts when we detect outages in your external dependencies! No more wasting time looking in the wrong place!
Try it out! How much time you'll save your team, by having the outages information close to them?