DEVHERO Write on WhatsApp
HelplineReal humans, not AI. Help within 24h
Human First
production is down

Production is down. We fix it within 24 hours.

The live site or API is down, or so degraded that customers cannot use it.

  • Health checks or the load balancer have nothing healthy behind them
  • Customers cannot sign in, pay, or load the core page
  • Error rates jump and stay high

One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.

A real senior specialist leads. Name on first reply. AI is a tool; a human checks the result.

01

The problem

What this problem looks like, how you can tell, and what is at stake if it stays.

What this problem looks like

What a production outage looks like, why every minute feels public, and why a calm specialist is useful in the middle of the noise.

Health checks fail and users cannot complete the job

Health checks fail. The load balancer has nothing healthy behind it. A deploy went wrong. A certificate, a disk, a database, a DNS change, or a dependency took the service with it. Status pages are already lighting up.

You are being asked for an ETA you do not have

Every minute feels public. You are being asked for an ETA you do not have. The team is in a call and still arguing about the first step.

Uptime is a promise you already made

Uptime is a promise you already made to your users, even if it was never written down. When production is down, that promise is already broken. The work is to restore it honestly.

You want it back, with a cause, not a reboot that will fail again in an hour.

When production is down, the live site or API is offline or so degraded that customers cannot use it. You want it back with a cause, not a reboot that will fail again in an hour.

More about how this shows up

A deploy, a certificate, a disk, a database, a DNS change, or a dependency can take the service with it. Status pages light up. The team is already on a call and still arguing about the first step.

Weekend work is a separate product; any surcharge is stated up front, before a call. We do not take every support request. We take a hard down system that needs an engineer.

Signs production is down, not just 'a bit slow'

These are signals that you are in an outage, even if one region or one path is still up.

Health checks or the load balancer have nothing healthy behind them

Instances fail, or they start and die in a loop.

Customers cannot sign in, pay, or load the core page

A marketing homepage may still be on a CDN while the app is dead.

Error rates jump and stay high

5xx, timeouts, or connection refused, across more than one user.

A deploy is in an unknown state

Some nodes moved, or a migration is mid-way, and nobody wants to touch it.

A dependency is down and your app has no fallback

DNS, a database, a queue, or a partner API is the real outage.

You have already restarted once and it fell over again

The reboot was not a cause, only a pause.

If it stays down, and if it comes back with a cause

Before — if you leave it

If you leave it

While it is down you lose sales, trust, and time from people who will remember the silence more than the later explanation.

After — if we close it

If we close it

Service is back, the immediate cause is known, and the unsafe workaround — if one was needed — is written down so it can be replaced.

Recognize your situation? Message us, we will sort it out.

02

Why it happens

Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.

Common causes of a production outage

Most outages have a last change, a saturated resource, or a dependency. Finding which one is the work.

A bad release or a bad configuration

A flag, a secret, a certificate, or a container image that only fails at live scale.

Database or disk exhaustion

Connections, locks, a full volume, or a migration that will not finish.

DNS, TLS, or routing changes

A record, a certificate, or a load-balancer rule that no longer points at healthy origins.

A dependency or a quota

A cloud limit, a payment of the account, or a third-party outage with no timeout.

A security or capacity event

An attack, a traffic spike, or a process that ran away after a deploy.

Why young stacks and generated deploys fail hard in public

A generated pipeline or a 'works on my machine' container will often meet production for the first time on a launch day. Fast startups also skip runbooks, so the first outage is also the first rehearsal.

A Human First incident still starts with the last change and the logs, not with a hopeful restart script written by a model in the middle of the call.

What to check first when the website is down

Capture evidence as you go. A reboot can help and also wipe the picture you needed.

  • Confirm the scope

    Which URLs, which regions, which users, and whether it is total or degraded.

  • Check the last change

    Deploy, DNS, certificate, cloud change, or a job. Write down the time.

  • Look at health of the app, the database, and the disk

    One of those is often already telling the truth.

  • See whether a rollback is obvious and safe

    A known last good artefact is a gift, if data allows it.

  • Note whether this might be a security incident

    Defacement, ransom, or unexpected admin. That changes the order of work. See also the hacked-website page.

Recognize your situation? Message us, we will sort it out.

03

How DevHero fixes it

A senior specialist leads. AI is a tool. A human checks the result.

Outages are chaotic. A calm specialist who has seen this shape of failure is useful precisely because you are in the middle of it.

DevHero is Human First. You write, you see a specialist's name, and that person can be alerted and called. AI may help us scan logs. A human leads the recovery and checks the fix. We do not take every support request. We take a hard down system that needs an engineer, not a help-centre script.

You write, you see a name, and that person can be alerted and called. AI may help us scan logs. A human leads the recovery and checks the fix.

How a typical weekday case moves

  1. 01Message received
  2. 02Specialist named
  3. 03Diagnosis
  4. 04Fix
  5. 05Human check
  6. 06Handover

How to get a specialist on a live outage

Write on WhatsApp or Telegram now. If you need to be first in the queue, ask about the urgent move to position 1. Weekend work is a separate product, with any surcharge stated up front.

  1. Say that production is down and what you already tried

    Times, URLs, last deploy, and whether you rolled back.

  2. A named specialist is alerted

    Within a minute you should see their name. They can be called if they do not respond.

  3. Restore a safe path, in 24 hours when in scope, often much sooner if the cause is clear

    A longer reliability programme is a complex project.

How DevHero works a production-down incident

We join the incident, restore a safe path to live, then tell you what still needs a lasting fix. A human checks the recovery.

We join the incident, look at the last change, the dependencies, the logs and the health of data, then restore a safe path to live. After it is up, we tell you what still needs a lasting fix. A longer reliability programme is a complex project. Weekend work is a separate product; any surcharge is stated up front, before a call.

  1. Join the timeline

    Last change, scope, and what has already been tried.

  2. Stabilise

    Rollback, failover, or a containment that brings the user job back, if that is safe.

  3. Find the cause with enough evidence

    Logs, health, disk, dependencies — without destroying the only copy of the trail if we can avoid it.

  4. Put a lasting fix in motion, or name it

    Some causes need a follow-up. We will not pretend a reboot is a root-cause analysis.

  5. Write down the unsafe workaround, if one was needed

    So it can be replaced.

What you get in the first hours of an outage, and within 24 hours

The first aim is to restore a safe path. The 24-hour aim, on a typical weekday case in scope, is a cause and a checked recovery.

  1. A specialist on the incident, named, once you are in the session.

  2. Service restored, or a clear containment, if that is possible with the access we have.

  3. A cause, or a narrowed set of causes, in plain language.

  4. A note of any workaround that must not stay.

  5. A human-checked recovery, and a follow-up if reliability work remains.

What to send us when production is down

Speed matters. A few facts prevent a blind restart. Do not paste live passwords into the chat.

URLs and the time it started

Plus the time zone.

What users see

Errors, blank pages, login failures, payments failing.

The last change

Deploy, DNS, certificate, or cloud event.

What you already tried

Restart, rollback, scale-up, or a failed failover.

How we can get on the system with you

An agreed channel and authorised access.

Quick and urgent fixes

First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.

Free (first session)

Complex projects

Larger work uses a different rate, on request. We say so before we continue.

On request

Weekdays, then weekends

The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.

On request

The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.

One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.

Recognize your situation? Message us, we will sort it out.

04

Stay fixed

What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.

What not to do in the middle of an outage

Motion is not the same as recovery. Some moves make the next hour harder.

Restarting everything before you capture logs

You may get a brief recovery and lose the cause.

Deploying a fresh guess on top of a stuck release

You can lose the last good artefact.

Debating the perfect post-mortem while it is still down

Restore first, then write.

Posting a detailed technical theory in public before you know it

You may be wrong, and you may reveal a path you have not closed if this is also a security event.

Ignoring the possibility of a breach

If the site was defaced or data is leaking, see the hacked-website and security pages and say so early.

Where we see production go down

Tell us the stack and the host. If we should not take it, we will say so.

Web apps and APIs on typical clouds and PaaS

AWS, GCP, Azure, and simpler hosts.

Databases and queues that take the app with them

Postgres, MySQL, Redis, and job workers.

DNS, TLS, and load balancers

The edge that can look like an application failure.

Release platforms

A CI/CD change that became an outage. See also failing deploys.

After production is back: how to make the next outage shorter

A recovery is incomplete if the same move would take you down tomorrow.

Right after the fix

Write the timeline while it is fresh

Cause, workaround, and the lasting fix.

Practise a rollback

A rollback you have never tried is a hope.

Add the missing health check on the user job

Not only on a static page.

Put timeouts and disk alarms where they were missing

Boring checks.

As you keep shipping

Separate irreversible data changes from the first-time deploy

When you can.

Agree who can be called, and how

A name and a path, not a group chat with fifty people.

Review generated deploy changes before they go live

A pipeline you do not understand will fail in public.

Recognize your situation? Message us, we will sort it out.

05

Questions about this problem

Straight answers about this problem, the session, and what happens next.

Should I already have rolled back?

If you have a known last good release and a safe rollback, say what you already tried.

What if this is a security incident, not a crash?

Say that. We will treat it with that order of work. See also the pages on a hacked website and on security holes.

Can I jump the queue?

Yes. Ask about the urgent move to position 1. The start price is 99 USD while the queue is empty, and it can be revised later.

How do I start?

Write on WhatsApp or Telegram now. No form, no web chat.

Do you work weekends as the default?

No. The base plan is weekdays. Weekend work is a separate product, and any surcharge is stated up front, before a call.

Will you invent an availability percentage?

No. We will talk about this incident and what we changed.

Can you stay on after it is back?

If you want a reliability follow-up, we offer the matching rate and we sign for that work.

Our status page is still green. Does that mean we are up?

Not if the user job is down. Health checks can be looking at the wrong thing.

Do you take every support ticket?

No. We take a hard down system that needs an engineer, not a help-centre script.

Is the first session really free?

Yes. Each client gets one free session: the first 4 hours with a specialist, plus unlimited AI as a tool. The 24-hour line is how quickly we aim to start and close a typical weekday case in scope, not 24 hours of unpaid work. Further work is paid, on request.

Human First

Production is down. We fix it within 24 hours.

If production is already down, write on WhatsApp or Telegram now. You will talk to a person.

One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.

Human First

Choose a channel

No web form, no web chat. Write on WhatsApp or Telegram and a specialist replies. Your message is prefilled with the problem and the page.

Telegram opens the chat with @brnzai. It may not paste this text automatically — copy it and send it there: