Blog

An expired SSL certificate can take your entire site offline — browsers show scary warnings, APIs reject connections, and users lose trust. It's one of the most preventable outages, yet it still catches teams off guard. Osminog now monitors your SSL certificates automatically.

How it works. When you verify a project with an HTTPS scheme, Osminog immediately checks the SSL certificate and starts daily monitoring. No extra setup — it's automatic for every HTTPS project.

What you see. On your project page and project cards, you'll find:

• Expiration date — when the certificate expires.
• Days remaining — color-coded badge: green (30+ days), yellow (8–30 days), red (7 days or less).
• Issuer — who issued the certificate (Let's Encrypt, GlobalSign, etc.).
• Last checked — when the last check was performed.

Timely notifications. You'll receive alerts at 7 days, 3 days, and 1 day before expiry — through all your configured channels: website bell, email, Telegram, and webhooks. Notification preferences are fully respected, so you can enable or disable SSL alerts independently.

Error detection. If the SSL connection fails entirely (misconfigured certificate, wrong hostname, etc.), the error is captured and displayed on the project card — so you know immediately when something is wrong beyond just expiry.

SSL monitoring is included in all plans, including the free tier. One less thing to worry about.

Ever wondered how your website handles a sudden spike in traffic? Now you can find out in seconds — no signup, no setup, no command-line tools. Just open the "Burst your website" popup on our homepage and paste your URL.

How it works. Enter a URL and hit Start. Osminog immediately begins sending HTTP requests to your website and renders a live chart of response times, status codes, and errors — right inside the popup. You'll see success rates (green), client errors (yellow), and server errors (red) plotted in real time.

Tune the load with sliders. Three sliders let you adjust the test on the fly — no need to stop and restart:

• Interval (1–30 seconds) — how often requests are sent. Crank it down to 1s for aggressive testing.
• Concurrency (1–5x) — how many parallel requests per tick. Set to 5x and watch your server handle (or not) a burst of simultaneous connections.
• Timeout (0.5–30 seconds) — how long to wait before declaring a request failed. Lower values surface slow endpoints faster.

Changes take effect instantly — the running task updates its parameters on the backend without restarting, so the chart stays continuous.

Aggregated status cards beneath the chart show per-status-code breakdowns with min/avg/max response times, giving you a quick health summary.

From trial to permanent monitoring. Like the results? A conversion flow lets you save the live task as a permanent monitoring task. Enter your business email, confirm via a link, and your account, project, and task are created automatically — with all collected data preserved.

Registered users get more power. If you already have an account, the same sliders appear on the results page for every task — with limits matching your plan. Adjust interval, concurrency, and timeout on the fly without leaving the chart. Changes are saved immediately via AJAX.

Try it right now — no account needed:

You can now invite colleagues and collaborate on monitoring together. Teams let you share projects, split responsibilities, and keep everyone in the loop — without sharing passwords.

Creating a team. Go to Teams, hit "New Team," pick a name and a URL slug. You're the owner. Add your first project or invite people right away.

Invitations. As the owner, click "Invite Member," enter an email address, and choose a permission level. The invitee receives an email with a join link. If they don't have an Osminog account yet, the invitation waits — they can sign up and accept it later. Pending invitations show up on their Teams page the moment they log in.

Permissions. Two roles keep things simple:

• Read — can view all team projects and monitoring results. Great for stakeholders who need visibility without touching anything.
• Write — can add and manage projects and tasks. Suitable for engineers who need full operational access.

Only the owner can invite members, change permissions, and manage the team itself.

Shared projects. Any project created under a team is visible to all active team members according to their permission level. Projects show who created them, task counts, and quick links to results and status pages.

Team dashboard. Each team has its own dashboard showing all shared projects at a glance — task status, running/paused counts, and direct links to project details. Owners also get access to member management, ownership transfer, and team deletion from the same page.

Ownership transfer. Need to hand the team over to a colleague? Pick an active member from the dropdown and transfer. They get an email notification and become the new owner instantly. You remain a member with Write access.

Teams are available on Pro and Business plans. Compare plans to get started.

The new Dashboard gives you a single place to watch all your monitoring tasks at once — no more jumping between project pages.

How it works. Open the Dashboard and click "Add Widget." A searchable list shows every monitoring task you have access to, including tasks from shared team projects. Pick one, and a widget card appears on your dashboard immediately.

What's in each widget. Each card shows:

• The monitored URL with a direct link to the full results page.
• A mini chart of response times — green for successful requests, yellow for 4xx errors, red for 5xx.
• Aggregated status counts (how many requests returned 200, 503, etc.) for the selected time range.
• The last incident — status code, start time, and duration — so you can spot patterns without opening the results page.
• A time range selector (1 min to 24 h) that persists across sessions.

Drag-and-drop layout. Grab any widget by the grip handle and drag it to a new position. The layout saves automatically. You can also toggle each card between half-width and full-width using the expand button in the header — useful for charts you want to see in more detail.

Team tasks. Widgets can include tasks from any team you're a member of, not just your own. This makes the Dashboard a natural operations centre for teams monitoring a fleet of services.

The Dashboard is available on all plans.

You can now send monitoring alerts to any URL — your own server, a Slack incoming webhook, a Discord channel, a PagerDuty endpoint, or any service that accepts HTTP POST requests.

How it works. Go to Account Settings and paste your webhook URL into the new "Webhook URL" field. Once saved, a Webhook toggle appears next to each notification type — threshold alerts, status changes, and recoveries. Enable exactly what you need.

What gets sent. Osminog sends a JSON POST request with a structured payload containing the notification type, monitored URL, HTTP status code or response time details, and an ISO 8601 timestamp. The Content-Type is application/json and the User-Agent is Osminog/1.0, making it easy to filter in your receiving service.

Example payload:

{
  "type": "status_change_error",
  "url": "https://example.com/api",
  "status_code": 503,
  "message": "HTTP status changed from 200 to 503",
  "timestamp": "2026-03-19T12:00:00+00:00"
}

Reliable delivery. Each webhook request has a 10-second timeout. If your endpoint is temporarily down, the failure is logged but won't affect your other notification channels — email, Telegram, and in-app notifications continue to work independently.

Webhooks are available on all plans. Combine them with Telegram and email for a multi-channel alerting setup that fits your workflow.

Your application doesn't live in a vacuum. It depends on AWS, Stripe, GitHub, Cloudflare, and dozens of other services. When one of them goes down, your users want to know: is it you, or your provider?

Starting today, you can add external dependencies to your Osminog status pages. Pick from a curated catalog of 27 popular services — cloud providers, payment gateways, CDNs, DevTools, email services, and more — and select the specific sub-components you rely on (e.g. AWS EC2 in us-east-1, Stripe Webhooks, GitHub Actions).

How it works. Open your status page settings, scroll to the new "External Dependencies" section, and add services. Choose the exact components and regions you care about, optionally set a custom display name (e.g. rename "Amazon EC2" to "Our Servers"), and save. That's it.

Automatic polling. Osminog checks the status of your dependencies every 2 minutes by fetching their public status feeds. Most major services use the Statuspage.io format, which we parse automatically. When a dependency degrades, the status on your page updates within minutes — no manual intervention.

Visible everywhere. Dependencies appear on the public status page, in the embeddable widget, and through the API. They're shown in a separate "Dependencies" section with the same status indicators your users already understand. If a dependency has an active incident, the message is shown inline.

Overall status impact. Dependency statuses factor into your page's overall status calculation. If Stripe is having a major outage and you depend on it, your overall banner reflects that — giving your users an honest picture.

The catalog currently includes: AWS, GCP, Azure, DigitalOcean, Hetzner, Cloudflare, Fastly, Stripe, PayPal, GitHub, GitLab, npm, Docker Hub, SendGrid, Mailgun, Postmark, Auth0, DNSimple, Datadog, Sentry, Twilio, Slack, MongoDB Atlas, Redis Cloud, Algolia, Vercel, and Netlify. We'll keep expanding it — let us know what services you'd like to see added.

You can now create public status pages for your websites — directly in Osminog. No code, no separate service, no extra cost on Pro and Business plans.

How it works. Go to any project's detail page and click "Create Status Page." Give it a title and slug (the public URL), add components linked to your monitoring tasks, and you're live. Your status page auto-updates based on real monitoring data — when a task starts returning errors, the component status changes instantly.

Auto-incidents. Enable the "Auto incidents" toggle and Osminog will automatically create incidents when monitoring detects failures, complete with HTTP status codes and timestamps. When the service recovers, the incident is resolved automatically with a timeline entry. No manual work needed.

Subscriber notifications. Visitors can subscribe to your status page with their email. When an incident is created, updated, or resolved, all confirmed subscribers receive an email notification with a direct link and an unsubscribe option.

Embeddable widget. Enable the widget, copy the JS snippet, and drop it on your own site. The widget fetches component status via API and renders a compact status card. CORS is restricted to your domain by default (configurable).

Customization. Choose light or dark theme, upload a logo, set a brand color, hide the "Powered by Osminog" footer (Business plan), and control what's visible — hide URLs, response times, or last check times per component.

Status pages are available on Pro and Business plans. Compare plans to get started.

You can now receive monitoring alerts directly in Telegram. No more checking email or the dashboard — threshold spikes and status changes will land in your chat instantly.

How it works. Go to Account Settings, find the new "Notification Bots" section, and click Connect next to Telegram. You'll get a secret key — open our bot in Telegram, send /start, then paste the key. That's it. The bot confirms, and you're connected.

Per-type control. Once connected, a Telegram toggle appears next to each notification type in your preferences — threshold alerts, status changes, and admin announcements. Enable exactly what you need, same as you do for email and web notifications.

What you'll get. Alerts include the monitored URL, HTTP status code or response time details, and a direct link to the results page. Messages are concise and formatted for quick scanning on mobile.

The results chart just got a major upgrade — more detail, better navigation, and clearer error visibility.

Separate error lines. Client errors (4xx) and server errors (5xx) are now drawn as distinct lines on the chart — yellow for 4xx, red for 5xx. Previously all errors were merged into a single red line, making it impossible to distinguish timeouts (408) from gateway errors (502). Now each category stands on its own.

Zoom in and out. Use the + / - buttons in the top-right corner of the chart to zoom into a specific time window. Each click trims or expands the view by one chart tick interval, so the zoom feels natural and predictable. The range dropdown switches to "Custom" while zoomed, and selecting any preset range resets the view.

Pan left and right. Once zoomed in, < / > buttons appear next to the range dropdown, letting you scroll through the timeline one step at a time. The current custom window is displayed between the buttons so you always know where you are. Buttons disable automatically when you reach the edge of the available data.

All these features work together: pick a range, zoom into a suspicious spike, then pan around to compare neighbouring intervals — all without reloading the page.

Two powerful features just landed in Osminog, giving you much more control over how your monitoring tasks behave.

Regex content search. The "Search text in response" field now supports regular expressions. Wrap your pattern in slashes — for example /\"status\":\s*\"ok\"/i — and Osminog will match it against the response body using a full regex engine. Plain text search still works the same way: just type the string without slashes. A built-in validator on the task form checks your regex before saving, so you'll never deploy a broken pattern.

Multiple custom headers. The "Custom Headers" authentication mode now accepts multiple headers, one per line. This means you can combine API keys, custom auth tokens, and any other headers your endpoint requires — all in a single task configuration. The format is simple: Header-Name: value, one per line.

Both features are available on Pro and Business plans. Happy monitoring!

After months of development, testing, and one very determined octopus, we're thrilled to announce that Osminog is officially live.

Osminog is a website monitoring platform built for developers and teams who care about uptime and performance. Here's what you get out of the box:

• HTTP monitoring with configurable intervals (from 1 second to minutes), supporting GET, POST, PUT, DELETE, PATCH, and HEAD methods.
• Real-time charts with live WebSocket updates — watch your response times as they happen.
• Instant alerts via email and in-app notifications when response times spike or HTTP status changes.
• Flexible authentication — Basic, Bearer, or custom headers to monitor protected endpoints.
• Concurrency modes — burst or distributed load patterns for stress testing.
• Content search — verify that response bodies contain expected text.
• REST API for automation and building custom dashboards or status pages.

Start with our free plan — no credit card required. When you're ready for more, Pro and Business plans unlock background monitoring, higher concurrency, custom headers, and longer data retention.

We have big plans ahead: public status pages, more notification channels, and multi-region checks. Stay tuned, and welcome aboard!