Skip to Content
Add-on · 24×7 NOC Access

24×7 emergency response for your Linux servers

Add 24×7 NOC coverage to your Proactive plan. Critical issues on covered servers get a 1-hour response commitment, day or night, backed by service credit if we miss.

▲ crafty-penguins / what-we-do / engagement-types / 24x7-noc-access
What it is

What 24×7 NOC Access is

NOC stands for Network Operations Center. This add-on gives your covered servers 24/7 monitoring with automatic dispatch to on-call engineers, plus a phone number and a portal for manual escalation when something urgent needs eyes.

Most infrastructure breaks at inconvenient times. Middle of the night. Saturday of a long weekend. First day of a launch. NOC coverage means someone senior is already responding when it does, not tomorrow morning, not when the team gets in. Now.

It layers on top of TLC Proactive Managed Services. Response time is charged to your Reactive Flex Time agreement at the appropriate rate.

24x7 infrastructure monitoring
What's in it for you

Why teams add NOC coverage

01

Coverage while you're offline

  • Someone senior is watching every hour, including nights and weekends
  • Issues get handled while your team sleeps, not filed for the morning
  • No gap between "something broke" and "someone's on it"
Around-the-clock coverage
02

Faster response, less downtime

  • A one-hour response commitment on every critical issue
  • Problems get caught and worked before they spread
  • Automated monitoring dispatches on-call engineers instantly
Fast response
03

Real engineers, one number

  • You reach senior Linux engineers, not a first-tier script
  • One phone line and portal, no vendor juggling mid-incident
  • The same team that already knows your environment
Senior engineers on call
04

Peace of mind

  • Your launch, the long weekend, and 3 AM are all covered
  • Protects revenue and reputation when uptime matters most
  • You get to step back from being the on-call escalation
Peace of mind
The guarantee

Our response time commitment

1 HOUR Response time SLA

For any managed client in good standing, we respond within one hour to any critical issue on covered servers. 24 hours a day. Every day.

What that means

One hour isn't an automated acknowledgement. It's a senior engineer actively responding to your critical issue, already working the problem while your team sleeps, any hour of any day of the year.

Who responds · a senior on-call engineer, not a script or a first-tier queue.
Real engineers
When · nights, weekends, and holidays included, not just business hours.
Every single day
How you reach us

How to activate NOC

Automated for the things a monitor can see. A phone number and a portal for the things it can't.

Method 01

Automated monitoring

24/7 · dispatch immediately

During onboarding we configure 24/7 automated monitoring on mission-critical metrics with our default thresholds. Alerts dispatch to the on-call engineer without you having to lift a finger.

Method 02

Call the NOC line

1-403-399-0790

Our 24/7 answering service verifies you're an authorized user on a NOC agreement, then dispatches to the on-call engineer. Available any hour of the day.

Method 03

Use the portal

portal.craftypenguins.net

NOC-agreement clients have an additional form in the portal that sends a NOC-level support request. Dispatches immediately to the on-call engineer.

What counts as critical

What qualifies as a critical issue

Category 01

Automatically detected

A specific, measurable event that our monitoring system identifies on its own. Alerts fire, on-call engineers are dispatched, the response clock starts.

Website down API failure Full disk drive Hard drive error Abnormal response time Out-of-memory error High rate of failed logins
Category 02

You phone it in

Any high-severity service-impacting issue you report for investigation. If your team sees something urgent that our monitors haven't caught yet, the phone line or portal is how you make it critical.

Symptoms your team is seeing Customer-impacting incidents Suspected security events Anything urgent enough to call at night
Requirements

Prerequisites for NOC coverage

NOC Access isn't a standalone product. It layers on top of an active managed engagement. Three things need to be true.

Requirement 01
Managed Client

You have an active monthly TLC Proactive agreement with maintenance, and onboarding and stabilization work has been completed.

Requirement 02
Good Standing

All monthly services paid by the first business day of the month. Reactive agreement paid and current. Not at your credit limit for overage.

Requirement 03
Covered Server

The server in question is on both a TLC Proactive plan and this 24×7 NOC add-on. The SLA applies per-server, not blanket to your whole fleet.

Required engagements

What this add-on layers onto

You'll need a Proactive agreement to designate covered servers, and a Reactive Flex Time agreement so response time can be billed against your allocation.

NOC in action

All success stories
Other engagements

Explore our other engagements.

There are a few different ways to work with us. Here are the other engagements you can explore.

Start the conversation

Ready to add NOC coverage?

A 30-minute conversation is enough for us to understand which servers should be covered, walk you through onboarding, and give you a quote for the monthly NOC agreement.