When a vendor goes down, have a clearer answer.
Statusfield shows vendor-reported incidents affecting the components you follow. Send relevant updates to the people responsible and give your team one place to check what’s happening.
Follow vendor-reported status across 7,000+ services.
30-day free trial — no card needed · First-time customers
Dashboard
Live health across your 36 monitored services
Fleet health
32 of 36 services fully operational
Active incidents
Dashboard illustration with sample data. Check the catalog for current vendor status.
Built for your team
Something stops working. People need answers. Bring vendor status into the work your team does next.
For engineering teams
Decide where to look next during an incident. Check reported cloud and API problems alongside your own monitoring, and keep engineering informed as vendors post updates.
Example services you can monitor
See the engineering workflowFor IT teams
Give staff a place to check when a business tool stops working. Bring vendor updates to IT and share a status board while you coordinate the response.
Example services you can monitor
See the IT workflowPrepare for the next vendor outage
Choose your dependencies, decide who gets updates, and test delivery before you need it. No installation or code changes.
Pick your services
Find your vendors in 7,000+ services. Choose the components and regions you use, where available.
Set your alert rules
Choose which status changes reach email, team chat, or on-call. Give each alert a destination.
Send a test alert
Send a labeled test alert. Confirm it arrives where you expect before relying on your setup.
Available channels depend on your plan. Activate monitoring to receive selected status changes and recovery updates.
Bring vendor context into your investigation
Check reported outages, affected components, and incident details together. Use that context alongside your own monitoring to decide where to investigate next.
Their services
7,000+ services watched
151,000+ components tracked
Down to the component
GitHub Actions, not just GitHub
Incident note attached
when the provider shares details
Recovery alerts
when the vendor reports recovery
Your services
Domains & SSL
expiring certs caught
Ping checks
your own endpoints
Internal systems
hand-set status, notes
Cloudflare is experiencing degraded performance.
We are investigating elevated latency and error rates across multiple data centers. Traffic is being rerouted while we work on a fix.
Get relevant updates to the people responsible
A major outage and a maintenance update don’t need the same response. Choose a destination for each status you want to follow, for the components and regions you use.
- Send major outage alerts to PagerDuty
- Send partial outages to your team’s chat channel
- Keep degraded-service updates in email
- Leave maintenance unrouted when you don’t need those alerts
Send vendor alerts to the right team
Choose from email, Slack, Microsoft Teams, and more. Channels depend on your plan.
Instant inbox alerts
Teams
Alerts in Teams channels
Slack
Native OAuth app
PagerDuty
Incidents that auto-resolve
Datadog
Events on your Datadog timeline
Webhooks
Any HTTP endpoint
API & MCP
Wire it into your own tools
Discord
Rich embed alerts
Telegram
Alerts in chats and groups
Give your team an answer they can check
When people ask whether a tool is down, point them to a shared view of vendor-reported status. Choose the services on your board so staff can check for updates while you coordinate the response.
- Share a read-only link, with optional password protection
- Email subscribers on paid plans: double opt-in, one-click unsubscribe
- Your logo and a custom URL on paid plans
- Create focused boards for different teams
- AWSMajor Outage
- GitHubOperational
- StripeOperational
- Office Wi-FiDegraded
Share status history and alert records
Review recorded status changes and alert deliveries. Export a Team-plan report for a vendor review or audit, covering the records available for your monitored period.
- Status history per vendor, per component, with durations
- Alert-delivery records: who was notified, when, on which channel
- Monitoring records to support your audit review
Reports require 30 days of workspace monitoring tenure. Coverage varies by vendor and retention; reports do not certify compliance.
See a sample evidence report“How do you monitor critical vendors?”
July 2026 · Client: Acme Co
Evidence ✓14
Incidents tracked
96
Alerts delivered
99.2%
Avg uptime
Stripe · Major Outage · Jul 14, 09:41–11:02
Report illustration with fictional company and incident data.
Simple, transparent pricing
Start with the alert channels and sharing your team needs, then check the monitor limits. Trial available for first-time customers. Cancel from your account.
Slack and Teams alerts for your team
- 15 monitors
- 1 board
- 150 subscribers
- 2 seats
On-call alerts and shared status boards
- 40 monitors
- 3 boards
- 600 subscribers
- 4 seats
Team monitoring and evidence reports
- 90 monitors
- 10 boards
- 1,200 subscribers
- 8 seats
- Monitoring evidence
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Frequently Asked Questions
Choosing your alerts, testing delivery, and finding the right plan.
Still have questions? Email us at support@statusfield.com. All emails are read by humans.
Be ready when your team needs answers.
Choose the vendors you depend on, route updates to the people responsible, and send a test alert before the next incident.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Start free trial