|
By Nuno Tomas
If you've been running production workloads on AWS for more than a year, you've felt it: the 3 am PagerDuty alert, the scramble to check the AWS console, the frantic Slack thread asking, "Is this us or is this AWS?" And then, minutes or hours later, the AWS Service Health Dashboard finally acknowledges what your users have been experiencing all along. It happens because AWS is the backbone of modern infrastructure.
Sponsored Post
|
By Nuno Tomas
The AWS Health Dashboard is slow, sometimes broken during major outages, and only tells you what AWS admits is broken. Real SREs layer three monitoring sources: AWS-native tools (CloudWatch, EventBridge), third-party aggregators (IsDown), and internal synthetic checks. Skip the vendor status page as your primary alert source.
|
By Nuno Tomas
In March 2026, IsDown users collectively saved 10.5 hours by receiving outage alerts before vendors officially acknowledged problems. The most significant early detection gave users a 2.3-hour head start when The Federal Reserve's FedACH system experienced issues. This data reveals the persistent gap between when users experience problems and when vendors update their status pages.
|
By Nuno Tomas
Your on-call phone goes off at 3:17 AM. Payments are failing. You ssh in, check your pods — all green. Database? Healthy. Load balancer? Fine. You spend 22 minutes chasing ghosts before someone checks Stripe's status page and sees the incident that started 34 minutes ago. Those 22 minutes are pure waste, and they're exactly the kind of MTTR you can reduce without touching a single line of your own code. And the fix isn't faster debugging. It's recognizing that the failure wasn't yours to debug.
|
By Nuno Tomas
If your product serves users in multiple regions, your status page widget shouldn't be stuck in English. A customer in São Paulo seeing "All Systems Operational" when they expect "Todos os Sistemas Operacionais" is a small friction, but small frictions compound. It signals that their language isn't a priority, and it adds cognitive load during the exact moment they're checking whether something is broken. Until now, IsDown widgets shipped with hardcoded English messages. That's changed.
|
By Nuno Tomas
This report covers the operational status of major AI systems during February 2026, including Anthropic, Cohere, DeepSeek, Google Gemini, Groq Cloud, OpenAI, Perplexity, Replicate, and xAI. The data includes official incidents reported on vendor status pages and unconfirmed incidents detected through IsDown's monitoring systems.
Sponsored Post
|
By Nuno Tomas
Every IT team eventually faces this question: should we build our own monitoring system or buy an existing solution? On the surface, building seems attractive. You get complete control, no vendor lock-in, and the illusion of "free" since you're using internal resources. But the math rarely works out that way. Let's break down what it actually costs to build, when building genuinely makes sense, and how to make the right decision for your team.
|
By Nuno Tomas
When SendGrid goes down, your transactional emails stop reaching customers. Password resets fail. Order confirmations vanish. Support tickets never arrive. By the time you notice, customers are already complaining. For DevOps and SRE teams, checking SendGrid status shouldn't be a manual process. It shouldn't wait until customers report it either. For a team sending 10,000 transactional emails per day, a 15-minute outage means roughly 100 emails that never arrived.
|
By Nuno Tomas
On February 17, 2026, YouTube went down for users worldwide. Starting around 8:00 PM ET, the platform's homepage, Shorts feed, sign-in system, smart TV apps, YouTube Music, and YouTube Kids all stopped working. Over 21,000 reports were logged on IsDown alone. The error message was the same everywhere: "Something went wrong." For consumer users, it was an inconvenience. For businesses that depend on YouTube — content teams, advertisers, media companies, live streamers — it was a blind spot.
|
By Nuno Tomas
At approximately 9:15 PM UTC on February 10, 2026, Amazon CloudFront began returning NXDOMAIN responses for DNS queries against specific distributions. In practical terms: DNS was telling users that services behind those distributions simply didn't exist. The root cause was a DNS resolution failure within CloudFront's infrastructure that quickly spread to eight interconnected AWS services.
- April 2026 (4)
- March 2026 (3)
- February 2026 (7)
- January 2026 (4)
- December 2025 (4)
- November 2025 (3)
- October 2025 (3)
- September 2025 (4)
- August 2025 (9)
- July 2025 (8)
- May 2025 (4)
- April 2025 (2)
- March 2025 (2)
- January 2025 (2)
- December 2024 (1)
- November 2024 (4)
- October 2024 (4)
- July 2024 (1)
- April 2024 (1)
- March 2024 (1)
- February 2024 (3)
- January 2024 (1)
- December 2023 (1)
- November 2023 (3)
- October 2023 (1)
- September 2023 (1)
- August 2023 (1)
- July 2023 (2)
- June 2023 (1)
- May 2023 (2)
- April 2023 (2)
- March 2023 (2)
- February 2023 (1)
- January 2023 (1)
- December 2022 (2)
- November 2022 (3)
- October 2022 (1)
- September 2022 (3)
- August 2022 (3)
- July 2022 (1)
- June 2022 (1)
- May 2022 (3)
IsDown is a status page aggregator & outage monitoring tool for all your business-critical dependencies. Easily monitor with a health dashboard with all your external services. Instant notifications on outages. All in one place.
It has never been easier to understand the outages in your external cloud services.
- 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.
- 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.
- 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.
- Dedicated dashboard for each team's services: Create one dashboard for each of your teams. Monitor only the services that each teams uses. Dedicated dashboard with custom notification settings.
- 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.
Easily Monitor Outages In All External Services. From One Place.