"super clean interface, very intuitive"
"incredible service"
"damn easy and foolproof to set up"
We alert you
when your API goes down.
Options for all types of requests
Want to test that your GraphQL API only responds to POST requests, and refuses GET requests? No worries.
Want to double check that your REST API rejects unauthenticated requests, the way you expect it to? Too easy.
Configure your API monitoring as you need, and OnlineOrNot will do the rest.
Alerts where you need them
Need to be absolutely sure we can reach you when things break? OnlineOrNot can send alerts via:
- SMS
- Slack/Discord
- Webhooks
Monitor correctness too
Your servers are responding, but is the data correct? Our powerful assertions feature helps you keep track of the data your API sends.
Say goodbye to false-positive alerts
When something goes wrong, OnlineOrNot double checks your API response from up to 18 locations around the world before sending you an alert.
Monitor, as a team
Keeping the lights on is your whole team's job, not the responsibility of just one person. OnlineOrNot is designed for teams in mind.
Don't lose track of your important API endpoints. With OnlineOrNot, your team can keep track of all of your APIs in one place.
Last week kept us busy
With plenty of room for more pages to check, incidents to catch, and notifications to send
- Pages checked
- 1,054,885
- Incidents caught
- 392
- Notifications sent
- 635
What others are saying about OnlineOrNot
Frequently asked questions
Here are the most frequently asked questions from our hundreds of users:
No time limit, and no credit card required.
The average cost of downtime for smaller businesses is around $137 to $427 per minute. For larger companies this rises to $5600 per minute, according to a 2014 study by Gartner.
While it's easier than ever to build websites and web apps, it's harder than ever to be sure they stay online.
Most teams struggle with two challenges when it comes to monitoring:
- Noisy, irrelevant alerts (so they miss important ones)
- Their tools are so slow and difficult to use that the team gives up on them
That's why I built OnlineOrNot — to make uptime monitoring better for teams.
Over the last 9 months we've checked over 52.3 million pages (like yours). I'd love you to give it a try.