When it broke this morning

Emergency Website, Software and App Repair: What to Do in the First Hour, and When to Call

The checkout stopped at 8:15. The phone has not rung since. Someone on the team is already typing "reinstall WordPress" into a search bar. Put the coffee down for one minute and read the order of work below first.

November 18, 2026 · 12 min read

acmebakeshop.com · emergency job log
One broken morning, in the order we work
Checkout down at 9:41, test order through by 11:02
Sample
  1. 09:41 Owner reports: checkout spins, no orders since 08:15
  2. 10:02 Outside check: home page 200, /checkout 500
  3. 10:06 Domain, SSL, host bill and status page: all current
  4. 10:11 Full backup of files, database and logs, as found
  5. 10:24 Error log: payment plugin fatal after auto-update
  6. 10:38 Plugin rolled back one version, staging then live
  7. 10:51 Test order placed and refunded; receipt arrived
  8. 10:55 Forms sent, phone link tapped, customer login works
  9. 11:02 Note to owner: what broke, what changed, what next
Illustrative: sample emergency job on a fictional bakery's online store

The short answer

Emergency repair means getting a broken website, web app or mobile app back to taking orders, calls and logins without making the damage worse: stop the harm, keep the evidence, check renewals, DNS and status pages, then fix the cause and test the money paths. DataCram responds the same business day. WordPress repairs have fixed prices from $149; everything else starts from $575, depending on complexity.

On this page
  1. Money stopped, data exposed, or doors locked: what makes it an emergency
  2. Six moves for the first hour, in the order that saves the most
  3. The quick fixes that turn a two-hour repair into a two-day one
  4. Three groups, 26 emergencies: find the one on your screen
  5. Same business day, fixed prices where we can, estimates where we cannot
  6. Five emergencies where the right call is not to us
  7. Cheaper than the next emergency: backups, monitoring and logins you own

Money stopped, data exposed, or doors locked: what makes it an emergency

Websites are full of broken things. A crooked photo, a dead link in an old blog post, a footer that still shows last year. None of that is an emergency. An emergency is a broken thing that is costing money or exposing data right now and gets more expensive every hour it stays broken. The test is short. If a customer tried to pay, call, book or sign in this morning and could not, you have one.

Treat it as an emergency

  • Checkout or payments stopped, or orders stopped arriving
  • Forms, booking or the phone link stopped sending leads
  • Customers or staff cannot sign in to the site, portal or app
  • The site shows a white screen, a server error or a browser warning
  • The app crashes on launch or vanished from the store
  • Someone may have taken data that is not theirs

Schedule it for this week instead

  • A layout that looks wrong but still works
  • A slow page that still takes orders
  • A slide in rankings over months, not overnight
  • The redesign you have wanted for a year
  • An app update that is still waiting in review

This section covers three kinds of systems, because they fail in different places. A website usually fails at the edges: an expired domain, a plugin update, a full disk at the host. Custom software and web apps fail in the middle: a deploy, a database, an integration whose key changed. Mobile apps fail at the gate: a certificate, a store review, a new phone operating system. Each group has its own offer page: emergency website repair, emergency software repair and emergency app repair.

Six moves for the first hour, in the order that saves the most

Panic has a direction. It points at the most dramatic button on the screen: reinstall, restore, delete, redeploy. Each of those can be the right move. Pressed first, each can destroy the one clue that explains what went wrong. Sequence beats speed. Here is the order we follow on our own jobs, and the one we would hand a friend over the phone.

  1. 1

    Write down what you see, with the time

    Screenshot the error, copy its exact wording and note when it started and who noticed. "The site is broken" is a mood. "Checkout returns a 500 error since 8:15" is a lead a developer can follow.

  2. 2

    Find out if it is down for everyone

    Run the address through our free is my site down check, then try it on a phone with Wi-Fi turned off. A problem that lives on one laptop is a cache or a network, not an outage.

  3. 3

    Rule out the boring causes before the scary ones

    Domain renewal, the hosting bill, the card on file, the SSL certificate, the Apple developer membership. Then the provider's own status page. Expired things look like catastrophes and are often the quickest repairs of all.

  4. 4

    Stop the harm, keep the evidence

    If the site is serving malware or the app is charging people wrongly, take that part offline. Copy the files, the database and the logs as they are, before anyone changes them. Do not reinstall over the problem.

  5. 5

    Ask what changed last

    A plugin update, a deploy, a new DNS record, a new iOS release, a password reset by someone who left. The last change is the first suspect, and undoing it is often the safest first repair.

  6. 6

    Fix the cause, then test the money paths

    When it works again, place a real order, submit every form, tap the phone number and sign in as a customer would. A home page that loads is not the same thing as a business that works.

If search traffic is the fear, a few hours of errors are not the end. Google's page on HTTP and network errors, read in November 2026, says server errors make its crawlers slow down for a while, and that pages already in the index stay there before they are "eventually dropped" if the errors persist. Google gives no number of days. The useful conclusion is to fix the cause properly today rather than rush a patch that fails again tomorrow.

The quick fixes that turn a two-hour repair into a two-day one

Emergencies tend to go badly in the same few ways. None of them involve stupidity. They involve a tired person, a forum thread from another decade and a button that promised to make the problem stop. Read this list before anyone touches the server.

Collage of a black server tower on fire beside a red fire extinguisher spraying foam and an open first-aid kit, on red and blue torn paper
Most of the damage in an emergency happens in the first hour, done by someone tired with good intentions.
  • Reinstalling over a hacked site. It throws away the evidence with the files, and a back door in the database or an untouched folder survives. Google's quarantine guide on web.dev, read in November 2026, says to take the site offline and tell the host first. Our malware removal page covers the cleanup that follows, and our website security services cover the quieter work beforehand: auditing, locking down and watching the scripts your pages borrow.
  • Restoring a backup nobody has tested. If last night's copy is infected or half written, you now have two problems and no clean original. Copy the broken state first, then restore somewhere separate.
  • Deleting logs to free disk space. The error log is the confession. A cleanup script that wipes it saves a little storage and costs hours of guessing.
  • Changing five things at once. New theme, new PHP version, new plugin, new host. If it works, nobody knows why. If it fails, nobody knows which change did it.
  • Asking Google for a review too soon. Google's Security Issues help, read in November 2026, says not to resubmit before a final decision, and warns that asking while the problem remains can get a site marked as a "repeat offender."
  • Switching off the server after a breach. The FTC's data breach guide for business, published in August 2023, says to take affected equipment offline but not to turn machines off until forensic experts arrive.
In the first hour, the order of work matters more than the speed of work.

Three groups, 26 emergencies: find the one on your screen

Every page below opens with the first steps you can take yourself, names the mistakes that make that particular failure worse, and says plainly when to call someone. Start with the row that matches what you see. If two match, start with the one that involves money or customer data.

Websites

Our website emergency offer covers WordPress, Shopify, other hosted builders, Next.js and hand-built sites. WordPress repairs have fixed prices; the rest get a written estimate.

Custom software and web apps

The software emergency offer covers portals, internal tools, databases, integrations and payment code, from $575 with a written estimate first.

iOS and Android apps

The mobile emergency offer covers crashes, store rejections and removals, certificates and logins, from $575 with a written estimate first.

What you are seeing, and the page to read first
What you are seeingRead this firstGroup
The site will not load at allWebsite down: the first 15 minutesWebsite
Spam pages, strange redirects or a red warningHacked website emergencyWebsite
The domain expired or company email stoppedDomain and DNS emergencyWebsite
A Next.js or Vercel deploy took the site downNext.js or React site downWebsite
Customers cannot pay at checkoutCheckout and payments downWebsite
Search traffic fell off a cliff overnightTraffic dropped overnightWebsite
The contact form went quietForms stopped sending leadsWebsite
The developer vanished with the loginsDeveloper disappearedWebsite
The Shopify store or its checkout is failingShopify store downWebsite
The web app returns errors or will not loadWeb app downSoftware
The database is down or records are missingDatabase emergencySoftware
The CRM or another integration stopped syncingAPI integration brokenSoftware
An update or deploy broke everythingFailed software updateSoftware
Customer data may have been takenData breach: the first hoursSoftware
Old software, no developer, and now it is failingLegacy software rescueSoftware
Card payments or renewals are failingPayment processing failingSoftware
The cloud host or server is downCloud server outageSoftware
Your SaaS is down and customers are askingTelling customers about an outageSoftware
The iPhone app crashes on launchiOS app crashingMobile
The Android app crashes or Play shows a warningAndroid app crashingMobile
Users cannot sign in to the appApp login brokenMobile
Apple rejected the update you need outApp Store rejectionMobile
The app broke after an iOS updateApp broke after an iOS updateMobile
Push notifications stopped arrivingPush notifications stoppedMobile
A certificate or provisioning profile expiredExpired Apple certificatesMobile
The app disappeared from the App StoreApp removed from the App StoreMobile

These pages are about the emergency itself. For the slower repair work that follows, our older service pages go deeper: fixing broken websites, fixing broken mobile apps, and the error library, which explains dozens of WordPress and platform error messages one at a time.

Same business day, fixed prices where we can, estimates where we cannot

When you call (210) 346-0848 or send the form below, we respond the same business day. Our hours are on the contact page. We do not promise nights, weekends or a reply in minutes, and we will not quote a fix time before we have seen the problem, because anyone who does is guessing. What we do promise is a straight account of what we see, what we need from you and what it will cost.

For WordPress, the most common emergencies have fixed prices you pay online from the matching repair page: site down or white screen $249, malware cleanup $349, a single WordPress error $149, a theme, builder or plugin conflict $199, and a speed fix $399. We start within one business day of payment, with a full refund if we can't fix it. The white screen repair page is a typical example, and the WordPress repair hub lists the rest.

Everything else, from a Shopify store to a custom portal to an iPhone app, starts from $575, depending on complexity, with a written estimate before any work starts. Broken connections to APIs and integrations are restored the same day once we have the access we need. The emergency pricing guide explains what moves the number, and our general pricing page covers new builds.

Five emergencies where the right call is not to us

A repair shop that says yes to everything is a sales office. Some emergencies need someone else first, and a few need nobody at all. If yours is on this list, we will say so on the first call and point you to the right door.

  • The provider is down, not you. If Shopify, Stripe, Vercel or AWS shows an incident on its own status page, nobody can fix it from your side. Post an honest note for customers and wait it out.
  • The fix is a renewal you can make yourself. If the domain lapsed and you hold the registrar login, renew it. ICANN's Expired Registration Recovery Policy, updated in February 2024, requires registrars to let the registrant at expiration renew the name. If who owns the name is in dispute, that is a question for your own attorney; laws differ by state.
  • You need a lawyer before a developer. If customer data may have been taken, your attorney, your insurer and, where relevant, law enforcement come first. We preserve evidence and repair systems; we do not give legal advice.
  • The traffic loss is slow, not sudden. A decline over months is a search problem, not a repair. Our website traffic dropped section covers that work.
  • Your own developer is answering. If the person who built it is reachable and capable, they know the code better than any newcomer. Call them first and keep our number as the backup.

Cheaper than the next emergency: backups, monitoring and logins you own

The cheapest emergency is the one a routine caught. Our hosting and maintenance plans start at $55 a month. That page describes managed hosting, updates checked on a staging copy before they reach the live site, daily off-server backups that are test-restored, security monitoring and uptime checks, all monthly with no long contract.

The other half is ownership. AWS's root user guidance, read in November 2026, recommends a business-managed email address that forwards to a group, which it says "reduces the risk of delays in responding, even if individuals are on vacation, out sick, or have left the business." As general practice, the same thinking fits your registrar, your host, your Apple developer account and your Google Play Console: company name, company address, more than one person able to get in.

A free website health check or site audit shows what is close to expiring or failing before it fails. If your custom software has no technical owner at all, a fractional CTO is the longer answer, and the emergency becomes a line item in someone's plan instead of a surprise on a Tuesday morning.

Everything in Emergency Repair

30 pages in this section.

More in Emergency Repair

30

Questions owners ask in an emergency

We respond the same business day; our hours are on the contact page. For WordPress Fix it now repairs, we start within one business day of payment. For everything else, work starts once you approve the written estimate. We do not promise a fix time before we have seen the problem, because the honest answer depends on what we find.

We do not promise nights or weekends. We respond the same business day during our posted hours. While you wait, the first-hour steps on this page are safe to take yourself: record the error, check whether the site is down for everyone, check renewals and status pages, and copy everything before anyone changes it.

Do not reinstall the platform over the problem, restore an untested backup on top of the broken copy, delete logs, or change several things at once. After a suspected breach, do not power machines off; the FTC's guide says to take them offline and wait for forensic experts. Each of those moves can erase the clue that explains the failure.

Use our free is my site down check, which tests the address from outside your network. Then open the site on a phone with Wi-Fi off. If it loads there, the problem is probably your office network, browser cache or DNS on one device, and you may not need a developer at all.

Usually, yes. We read the code and the setup before we change anything, and we say plainly if a repair is sensible or if something else is the better use of your money. We need access you control. If the original developer holds the logins and stopped answering, start with our page on a developer who disappeared.

No one can promise rankings. Google's documentation says that once a server answers normally again, it gradually raises its crawl rate, and that pages are dropped only when errors persist, with no number of days given. Fixing the cause cleanly, rather than patching it twice, is the best thing you can do for search after an outage.

Keep reading

Free · No obligation

Tell us what broke and when it started

Describe what you see and what changed last. We respond the same business day with what we think is wrong, what we need from you, and either a fixed price or a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote