nwilhelm logo and current status indicator

nwilhelm Status

Operational

nwilhelm.io ↗3 top-level components

checked Nov 3, 2026 9:44 PM UTC · nwilhelm's official status page

Is nwilhelm Down Right Now?

No. nwilhelm is up and running.

nwilhelm is currently operational with all systems functioning normally.

All components operational

Last broke
Nov 1
Uptime
99.95%
Most impacted
Emails

History · 30 day period

Service health

Service health, last 30 days

Oct 5Today
Vendor-reported incidentNo status degradation recordedDegradedMajor outageMaintenance

How to read this

The record

30 day period · not affected by the range above
Availability
99.95%
Last Incident
Major Outage
Nov 1, 2026 3:46 PM UTC
Incidents
2
1 major, 1 degraded
Most impacted
Emails
Longest 2h 2m

Availability counts operational or degraded time as available, averaged equally across all monitored components. Partial outages count as half downtime and major outages count in full, scheduled maintenance is excluded from the calculation, and periods with no recorded status are counted as available rather than assumed down. Each component is tracked independently to give you a clear picture of overall service reliability.

Get updates without checking back

Get email updates for the reported nwilhelm status changes you choose. Follow your other dependencies in the same workspace.

30-day free trial, no card needed. First-time customers; continued monitoring requires a paid subscription.

Recent nwilhelm outages & status updates

Status changes and service events for nwilhelm over the last 30 days

2 incidents over 30 days29 clear days · worst 1 on Oct 9
nwilhelm incidents per day over the last 30 days, one row per week
SMTWTFS
Oct 4
1
Oct 11
Oct 18
Oct 25
Nov 1
1
01 incident

Core Services experienced a major outage

Nov 1 · resolved after 2h 2m

Email Outage

Nov 1 · reported by nwilhelm · resolved

Scheduled maintenance on Core Services

Oct 10 · resolved after 2h 3m

3rd Party Services experienced degraded performance

Oct 9 · resolved after 7h 11m

Solid — we detected itHollow — nwilhelm reported it
View all incidents →

nwilhelm component status

Check current status by component. Open one for regions, incident details, and alerts.

What is nwilhelm?

More Other services

Frequently asked questions about nwilhelm

Common questions about monitoring nwilhelm and understanding service status

Is nwilhelm down right now?

nwilhelm's status source currently reports Operational. Last checked Nov 3, 2026 9:44 PM UTC. Statusfield tracks 3 components. A reported operational state does not rule out a local problem or an incident the provider has not yet reported.

How do I get notified when nwilhelm goes down?

Create a Statusfield account, select the nwilhelm components you depend on, and configure notification channels and status filters. Alerts follow detected changes that match your monitoring settings. Available channels and limits depend on your plan; delivery timing also depends on the source update and successful checks.

Why monitor nwilhelm alongside my other vendors?

Statusfield brings nwilhelm's reported component status together with your other vendors in one dashboard. You can choose the components you depend on and configure notification channels and status filters. The available channels and limits depend on your plan. Vendor status pages differ in their own subscription options.

What do nwilhelm status levels mean?

nwilhelm status levels indicate service health: Operational (all systems working normally), Degraded Performance (reduced functionality), Partial Outage (some components affected), Major Outage (significant service disruption), and Under Maintenance (scheduled maintenance). Statusfield tracks these statuses across 3 components to provide granular monitoring.

What should I do when nwilhelm is down?

When nwilhelm is down: 1) Check the affected components and any available incident updates, 2) Review your application's nwilhelm integration for fallback mechanisms, 3) Check the provider's support channels for recovery information, 4) Configure Statusfield alerts for detected status changes. Recovery times depend on the incident; Statusfield does not predict when the provider will restore service.

Has nwilhelm been down today?

The status timeline above is the record: it shows every incident, outage and maintenance window Statusfield has seen for nwilhelm over the last 30 days, with the times each began and ended. nwilhelm is not reporting a disruption right now; check the timeline for anything earlier today.

Why is nwilhelm not working for me?

If nwilhelm isn't working: 1) Check Statusfield to confirm if there's a service-wide outage, 2) Verify your internet connection, 3) Clear your browser cache and cookies, 4) Try accessing nwilhelm from a different network or device, 5) Check nwilhelm's official status page for regional issues. If nwilhelm shows operational but you're still experiencing issues, the problem may be local to your account or network.

Is nwilhelm down for everyone or just me?

Statusfield displays the status reported for 3 nwilhelm components. Compare the affected components with your own errors and the provider's latest updates. An operational status does not rule out a regional, account-specific, or unreported problem.

How can I reduce alert fatigue from nwilhelm status emails?

Use Statusfield to consolidate your dependencies into one dashboard. Choose which nwilhelm components to monitor, select the notification channels included in your plan, and configure status filters so routine updates do not go to the same destination as major outages.

How do I set up nwilhelm monitoring in 3 steps?

1) Create a Statusfield account — eligible new accounts can choose a free trial, no card required. 2) Search for "nwilhelm" in the service catalog and click "Monitor" to add it to your dashboard. 3) Configure the notification channels included in your plan and choose which severities should trigger alerts.

What notification channels does Statusfield support for nwilhelm alerts?

Route nwilhelm status changes to email, Slack, Microsoft Teams, PagerDuty, Discord or HTTP webhooks, depending on your plan. Choose the supported components and events that matter to your team, then test the destination and confirm your routing rules. Delivery depends on detected changes, source availability and the destination.

nwilhelm isn't the only vendor you depend on — and an outage at any of them looks the same to your customers.

Get alerted when any vendor in your stack has an incident

Free, no signup. Public DNS signals only.