[{"data":1,"prerenderedAt":558},["ShallowReactive",2],{"\u002Fblog\u002Finstant-website-downtime-alerts":3},{"id":4,"title":5,"author":6,"body":8,"category":547,"date":548,"description":549,"extension":550,"image":551,"lastUpdated":551,"meta":552,"navigation":437,"path":553,"readingTime":554,"seo":555,"stem":556,"__hash__":557},"blog\u002Fblog\u002Finstant-website-downtime-alerts.md","How to Get Instant Alerts When Your Website Goes Down",{"name":7},"Vantaj Team",{"type":9,"value":10,"toc":519},"minimark",[11,15,18,23,26,93,96,103,107,110,115,118,144,147,151,175,178,182,185,189,192,221,224,228,231,251,258,262,265,275,290,294,297,300,304,307,311,317,321,346,349,353,356,360,363,367,370,374,377,381,384,388,391,396,416,419,423,426,482,486],[12,13,14],"p",{},"Every minute your website is down costs you users, revenue, and trust. The difference between a 2-minute outage and a 45-minute outage usually comes down to one thing: how fast you found out.",[12,16,17],{},"This guide walks you through setting up instant downtime alerts - from picking a monitoring tool to configuring escalation so the right person gets paged even at 3 AM.",[19,20,22],"h2",{"id":21},"what-instant-actually-means-in-website-monitoring","What \"Instant\" Actually Means in Website Monitoring",[12,24,25],{},"No monitoring service is truly instant. Every tool has a check interval - the gap between consecutive tests of your endpoint. Common intervals:",[27,28,29,45],"table",{},[30,31,32],"thead",{},[33,34,35,39,42],"tr",{},[36,37,38],"th",{},"Check interval",[36,40,41],{},"Time to detect outage",[36,43,44],{},"Best for",[46,47,48,60,71,82],"tbody",{},[33,49,50,54,57],{},[51,52,53],"td",{},"30 seconds",[51,55,56],{},"30s - 1 min",[51,58,59],{},"Production APIs, payment flows",[33,61,62,65,68],{},[51,63,64],{},"1 minute",[51,66,67],{},"1 - 2 min",[51,69,70],{},"Most SaaS applications",[33,72,73,76,79],{},[51,74,75],{},"5 minutes",[51,77,78],{},"5 - 10 min",[51,80,81],{},"Lower-priority services, staging",[33,83,84,87,90],{},[51,85,86],{},"10+ minutes",[51,88,89],{},"10+ min",[51,91,92],{},"Free tier tools",[12,94,95],{},"A 1-minute check interval means you find out within roughly 1-2 minutes of the outage starting. That is fast enough for most teams. Free monitoring tools often run 5-10 minute intervals, which adds 8 minutes of undetected downtime per incident.",[12,97,98,102],{},[99,100,101],"strong",{},"The real bottleneck is usually alert delivery, not detection."," A monitor can confirm an outage in 30 seconds but still take 5 minutes to notify you if email delays or Slack rate limits get in the way.",[19,104,106],{"id":105},"step-1-set-up-uptime-monitoring","Step 1: Set Up Uptime Monitoring",[12,108,109],{},"You need a tool that sends requests to your endpoint on a schedule and detects failures.",[111,112,114],"h3",{"id":113},"what-to-monitor","What to monitor",[12,116,117],{},"Pick endpoints that reflect real user functionality:",[119,120,121,129,135,141],"ul",{},[122,123,124,125],"li",{},"Your homepage: ",[126,127,128],"code",{},"https:\u002F\u002Fyourdomain.com",[122,130,131,132],{},"Your API health check: ",[126,133,134],{},"https:\u002F\u002Fapi.yourdomain.com\u002Fhealth",[122,136,137,138],{},"Your login page: ",[126,139,140],{},"https:\u002F\u002Fapp.yourdomain.com\u002Flogin",[122,142,143],{},"Critical user flows: checkout endpoint, payment processor callback URL",[12,145,146],{},"Avoid monitoring CDN-cached pages for outage detection. A CDN returns 200 from cache even when your origin server is down.",[111,148,150],{"id":149},"how-to-add-a-monitor-in-vantaj","How to add a monitor in Vantaj",[152,153,154,157,163,166,169,172],"ol",{},[122,155,156],{},"Sign up at vantaj.com",[122,158,159,160],{},"Click ",[99,161,162],{},"Add Monitor",[122,164,165],{},"Paste your URL",[122,167,168],{},"Set check interval (1 minute for production endpoints)",[122,170,171],{},"Set expected status code (200 for most endpoints)",[122,173,174],{},"Save - monitoring starts immediately",[12,176,177],{},"Vantaj runs checks from 10 global probe regions and uses multi-region consensus before alerting. If only one region sees a failure, it does not alert. All regions must confirm before a notification fires.",[19,179,181],{"id":180},"step-2-connect-your-alert-channels","Step 2: Connect Your Alert Channels",[12,183,184],{},"The monitor is useless if the alert goes somewhere nobody watches. Connect the channels your team actually uses.",[111,186,188],{"id":187},"slack-alerts","Slack alerts",[12,190,191],{},"Slack is the fastest way to get a downtime notification to your engineering team during working hours.",[152,193,194,204,207,218],{},[122,195,196,197,200,201],{},"In Vantaj, go to ",[99,198,199],{},"Integrations"," > ",[99,202,203],{},"Slack",[122,205,206],{},"Authorize the workspace connection",[122,208,209,210,213,214,217],{},"Choose the channel for alerts (e.g., ",[126,211,212],{},"#incidents"," or ",[126,215,216],{},"#on-call",")",[122,219,220],{},"Test the connection",[12,222,223],{},"When a monitor fails, Vantaj posts a message to your chosen channel with the monitor name, failure time, affected regions, and a direct link to the incident.",[111,225,227],{"id":226},"email-alerts","Email alerts",[12,229,230],{},"Email works for after-hours coverage when Slack notifications are muted.",[152,232,233,242,245,248],{},[122,234,235,236,200,239],{},"Go to ",[99,237,238],{},"Alert Contacts",[99,240,241],{},"Add Contact",[122,243,244],{},"Enter the email address",[122,246,247],{},"Verify the address",[122,249,250],{},"Assign the contact to a monitor or alert policy",[12,252,253,254,257],{},"Use a group email address (e.g., ",[126,255,256],{},"oncall@yourcompany.com",") so the alert reaches whoever is on rotation.",[111,259,261],{"id":260},"webhook-alerts","Webhook alerts",[12,263,264],{},"Webhooks let you push downtime events to any system that accepts HTTP callbacks - PagerDuty, OpsGenie, custom scripts, or internal tooling.",[266,267,272],"pre",{"className":268,"code":270,"language":271},[269],"language-text","POST https:\u002F\u002Fyour-endpoint.com\u002Fhooks\u002Fdowntime\nContent-Type: application\u002Fjson\n\n{\n  \"monitor\": \"Production API\",\n  \"status\": \"down\",\n  \"region\": \"us-east-1\",\n  \"started_at\": \"2026-06-28T14:23:00Z\",\n  \"url\": \"https:\u002F\u002Fapi.yourdomain.com\u002Fhealth\"\n}\n","text",[126,273,270],{"__ignoreMap":274},"",[152,276,277,284,287],{},[122,278,235,279,200,281],{},[99,280,199],{},[99,282,283],{},"Webhooks",[122,285,286],{},"Paste your webhook URL",[122,288,289],{},"Choose which events trigger it (down, recovery, or both)",[111,291,293],{"id":292},"sms-alerts","SMS alerts",[12,295,296],{},"SMS works when Slack and email are not enough - during major incidents or for on-call engineers without app notifications enabled.",[12,298,299],{},"Vantaj includes SMS on Team and Enterprise plans. Add a phone number as an alert contact and assign it to your critical monitors.",[19,301,303],{"id":302},"step-3-configure-escalation-policies","Step 3: Configure Escalation Policies",[12,305,306],{},"An escalation policy defines what happens when nobody responds to an alert. Without one, a 3 AM outage can go unacknowledged until someone wakes up.",[111,308,310],{"id":309},"basic-escalation-model","Basic escalation model",[266,312,315],{"className":313,"code":314,"language":271},[269],"Alert fires\n  └── Notify primary on-call (Slack + email)\n        └── No acknowledgment in 5 minutes\n              └── Notify secondary on-call (SMS + email)\n                    └── No acknowledgment in 10 minutes\n                          └── Notify team lead (phone call)\n",[126,316,314],{"__ignoreMap":274},[111,318,320],{"id":319},"setting-up-escalation-in-vantaj","Setting up escalation in Vantaj",[152,322,323,331,334,337,340,343],{},[122,324,235,325,200,328],{},[99,326,327],{},"Alert Policies",[99,329,330],{},"New Policy",[122,332,333],{},"Add Step 1: notify your primary contact via Slack and email",[122,335,336],{},"Set escalation delay: 5 minutes",[122,338,339],{},"Add Step 2: notify secondary contact via SMS",[122,341,342],{},"Set escalation delay: 10 minutes",[122,344,345],{},"Add Step 3: notify team lead",[12,347,348],{},"Assign the policy to your critical monitors. Monitors on less critical services can use a simple \"email only\" policy.",[19,350,352],{"id":351},"step-4-avoid-alert-fatigue","Step 4: Avoid Alert Fatigue",[12,354,355],{},"Fast alerts only help if your team trusts them. A monitoring setup that fires false positives trains engineers to ignore notifications.",[111,357,359],{"id":358},"use-multi-region-verification","Use multi-region verification",[12,361,362],{},"Single-region checks generate false positives when there is a network blip between the probe and your server. Multi-region consensus checks from multiple locations before alerting. Vantaj does this by default.",[111,364,366],{"id":365},"set-realistic-timeout-thresholds","Set realistic timeout thresholds",[12,368,369],{},"If your API usually responds in 800ms but occasionally takes 1.5s under load, a 1-second timeout threshold fires alerts on normal variance. Set your timeout at 2x your p99 response time.",[111,371,373],{"id":372},"require-consecutive-failures","Require consecutive failures",[12,375,376],{},"Require 2 consecutive failures before alerting rather than triggering on the first missed check. This adds one check interval of detection delay (30-60 seconds) but eliminates most transient noise.",[111,378,380],{"id":379},"use-maintenance-windows","Use maintenance windows",[12,382,383],{},"Schedule maintenance windows during deployments. Alerts fired during planned downtime teach your team to ignore alerts during unplanned downtime.",[19,385,387],{"id":386},"step-5-test-your-alert-pipeline","Step 5: Test Your Alert Pipeline",[12,389,390],{},"Set up your monitors, connect your channels, and then test the full pipeline before you rely on it.",[12,392,393],{},[99,394,395],{},"How to test:",[152,397,398,404,407,410,413],{},[122,399,400,401,217],{},"Add a monitor pointing to a URL that does not exist (e.g., ",[126,402,403],{},"https:\u002F\u002Fyourdomain.com\u002Ftest-downtime-404",[122,405,406],{},"Wait for the alert to fire",[122,408,409],{},"Confirm it arrives in every channel you configured (Slack, email, SMS)",[122,411,412],{},"Check the response time from monitor trigger to alert receipt",[122,414,415],{},"Delete the test monitor",[12,417,418],{},"Do this once when you set up monitoring, and again after any change to your alert policy or notification channels.",[19,420,422],{"id":421},"quick-reference-checklist","Quick-Reference Checklist",[12,424,425],{},"Before you go live, verify:",[119,427,430,440,446,452,458,464,470,476],{"className":428},[429],"contains-task-list",[122,431,434,439],{"className":432},[433],"task-list-item",[435,436],"input",{"disabled":437,"type":438},true,"checkbox"," Critical endpoints are monitored at 1-minute intervals or faster",[122,441,443,445],{"className":442},[433],[435,444],{"disabled":437,"type":438}," Monitoring runs from multiple probe regions",[122,447,449,451],{"className":448},[433],[435,450],{"disabled":437,"type":438}," Slack or Teams channel receives downtime alerts",[122,453,455,457],{"className":454},[433],[435,456],{"disabled":437,"type":438}," Email alert goes to a monitored address, not a personal inbox",[122,459,461,463],{"className":460},[433],[435,462],{"disabled":437,"type":438}," Escalation policy covers after-hours outages",[122,465,467,469],{"className":466},[433],[435,468],{"disabled":437,"type":438}," SMS or phone call configured for critical services",[122,471,473,475],{"className":472},[433],[435,474],{"disabled":437,"type":438}," Alert pipeline tested end-to-end",[122,477,479,481],{"className":478},[433],[435,480],{"disabled":437,"type":438}," Maintenance windows scheduled for upcoming deployments",[19,483,485],{"id":484},"related-guides","Related Guides",[119,487,488,495,501,507,513],{},[122,489,490],{},[491,492,494],"a",{"href":493},"\u002Fblog\u002Fcomplete-guide-uptime-monitoring","Complete Guide to Uptime Monitoring",[122,496,497],{},[491,498,500],{"href":499},"\u002Fblog\u002Freduce-false-positive-alerts","How to Reduce False Positive Alerts",[122,502,503],{},[491,504,506],{"href":505},"\u002Fblog\u002Fmonitor-website-availability-multiple-countries","How to Monitor Website Availability from Multiple Countries",[122,508,509],{},[491,510,512],{"href":511},"\u002Fblog\u002Fwhy-website-keeps-going-down","Why Your Website Keeps Going Down",[122,514,515],{},[491,516,518],{"href":517},"\u002Fblog\u002Fbest-uptime-monitoring-tools","Best Uptime Monitoring Tools in 2026",{"title":274,"searchDepth":520,"depth":520,"links":521},2,[522,523,528,534,538,544,545,546],{"id":21,"depth":520,"text":22},{"id":105,"depth":520,"text":106,"children":524},[525,527],{"id":113,"depth":526,"text":114},3,{"id":149,"depth":526,"text":150},{"id":180,"depth":520,"text":181,"children":529},[530,531,532,533],{"id":187,"depth":526,"text":188},{"id":226,"depth":526,"text":227},{"id":260,"depth":526,"text":261},{"id":292,"depth":526,"text":293},{"id":302,"depth":520,"text":303,"children":535},[536,537],{"id":309,"depth":526,"text":310},{"id":319,"depth":526,"text":320},{"id":351,"depth":520,"text":352,"children":539},[540,541,542,543],{"id":358,"depth":526,"text":359},{"id":365,"depth":526,"text":366},{"id":372,"depth":526,"text":373},{"id":379,"depth":526,"text":380},{"id":386,"depth":520,"text":387},{"id":421,"depth":520,"text":422},{"id":484,"depth":520,"text":485},"tutorials","2026-06-29","Learn how to set up instant website downtime alerts via Slack, email, SMS, and webhooks. Covers monitoring setup, alert channels, escalation policies, and how to avoid false positives.","md",null,{},"\u002Fblog\u002Finstant-website-downtime-alerts",9,{"title":5,"description":549},"blog\u002Finstant-website-downtime-alerts","G8w-eq3jazFkWjvazjt6dMx5mZMxmaAGtPEdYyoa2_M",1782668041924]