01 / 06 Website down
Urgent help when a business website or store is down, broken after an update, or blocking orders — on almost any CMS, stack, cloud, or web host.
02 / 06 Critical functions failing
We trace business-critical failures from the visitor action to the system that should receive it, then repair the smallest safe point of failure.
03 / 06 Infrastructure or security failure
When the host says “application” and the vendor says “hosting,” we check both sides and show which layer is actually broken.
04 / 06 Diagnose before editing
We stabilize the decision-making first so an urgent edit does not turn one fault into three.
05 / 06 Isolate, repair, validate
The repair is only complete when the affected journey works for a real visitor, not merely when the admin screen looks calm.
06 / 06 Restored and verified
The same technician handles triage, repair, and notes, then recommends only the maintenance, hosting, backup, monitoring, or hardening that directly reduces repeat risk.
Our promise
If the fault we repaired comes back within 30 days, we repair it again at no charge. It applies to the problem we were hired to fix — not a new, unrelated failure — and we say plainly which of the two we are looking at.
What you get
We stabilize the live site first, then tell you what broke and what to do next. WordPress is common — it is not the limit.
HTTP 500 errors, white screens, failed updates, broken layouts, redirects, and checkout or login problems on any CMS or app.
WordPress, Drupal, Joomla, Sitefinity, Squarespace, Wix, Laravel, Node.js, custom PHP, and other stacks we can reach and diagnose.
WooCommerce, Shopify, Magento, BigCommerce, and PrestaShop: carts, payments, shipping, product pages, and order emails.
Contact forms, SMTP, DNS records, spam filtering, and notification routing checked from form submit to inbox.
Expired certificates, mixed content, redirect loops, DNS changes, Cloudflare settings, and domain cutover problems.
Injected spam, rogue redirects, backdoors, and hacked admin accounts. We triage the emergency here; full cleanup and hardening runs on our dedicated page.
From experience
From our team’s years of agency support work, emergency calls cluster around a short list of failures. We start there instead of rebuilding the site on day one.
White screens, fatals, intermittent 500s, or a site that stopped loading after nothing “changed” on the business side.
A PHP or runtime upgrade, a disk filling up, or a rewrite rule the host applied overnight.
A plugin, theme, or compiled file that does not survive the last update.
Storefront down while wp-admin or the Magento backend still loads — often DNS, cache, or nameservers, not the CMS.
Exhausted memory, malformed redirects, or a database that will not answer.
The outage is the emergency; the silent mail failure is what you discover after the homepage returns.
From experience
Anonymized examples from recent support work (2025–2026). Incomplete outcomes stay incomplete — we do not invent a clean ending.
2026
2026
2026
2026
2026
Rewritten from internal notes. No client names. Dated in the current 2025–2026 window.
First 15 minutes
Do these in order before anyone edits production. Print or save this page if you want a copy beside the keyboard.
Print this page to keep a paper copy beside the work.
This is the sequence we use on emergency repairs. It is not a service-level promise.
Verified Metro Vancouver IT work
Named clients, with consent, from work we delivered as Metro Vancouver IT.
Marine retail · Richmond
Managed WordPress hosting and search engine optimization for a long-running inflatable boat and marine accessories business.
Glass manufacturing · BC
A hacked website recovered and stabilized with ongoing WordPress hosting and uptime support — in a case where no backup was available.
Not only WordPress
WordPress emergencies are frequent, so they show up in our examples. The repair work is not limited to WordPress. If the site is Drupal, Joomla, Sitefinity, Squarespace, Wix, a Shopify or Magento store, WooCommerce, a Laravel or other PHP application, a Node.js app, or a custom CMS, we still start the same way: confirm what visitors see, find whether the failure is DNS, SSL, hosting, code, database, checkout, or malware, then apply the smallest safe fix.
The same is true of the platform underneath. We work on Microsoft Azure, Amazon Web Services, Google Cloud, managed and self-managed Linux VPS, Windows Server and IIS, cPanel and Plesk accounts, dedicated servers, and everyday shared web hosting. Hosting support saying “it is an application problem” while the application vendor says “it is hosting” is a normal starting point — we sit in the middle and prove which side is actually broken.
When the symptoms look like a hack — spam pages, unexpected redirects, new admin users, blacklists, or files that keep coming back — we treat it as an incident rather than a bug. Triage still starts here, and the cleanup itself is scoped on our WordPress malware removal page: snapshot first where access allows, remove the malware, close the entry point, and leave you with plain-English notes instead of a mystery restore.
The fastest repair path usually needs CMS or app admin, hosting or cloud panel (cPanel, Plesk, Azure, AWS, or similar), SFTP/SSH or Windows RDP when available, DNS registrar or Cloudflare access, and any recent change history. If access is missing or compromised, we start by helping recover the safest control point.
Platforms we repair
If it is a website or store we can reach, we will triage it. These are the stacks we see most often — not a closed list.
White screens, critical errors, plugin conflicts, checkout failures, and admin lockouts.
Broken carts, payment apps, shipping rules, theme errors, and order notifications that stopped sending.
Module conflicts, failed updates, login issues, and sites stuck after a vendor or PHP change.
Fatal errors, database connection failures, process crashes, and legacy code that still has to take orders today.
App Service, VMs, load balancers, certificates, DNS, and resource limits that take a site offline.
VPS, dedicated, cPanel, Plesk, IIS, and shared hosting — we diagnose the box before guessing at the app.
Symptoms we fix
Our process
The goal is to stabilize the site first, then leave you with a short list of what changed and how to prevent the same failure.
Confirm the symptom, business impact, recent changes, and available access. We identify whether the first move is hosting, DNS, SSL, CMS, code, database, or malware.
Take a fresh backup or hosting snapshot where possible before making risky changes, even if the current state is already broken.
Review logs, runtime version, disk space, DNS, SSL, recent CMS or package changes, form delivery, and database connectivity before editing production.
Apply the smallest fix that stabilizes the site: rollback, patch, disable a conflict, restore a file, remove malware, correct DNS, renew SSL, or repair mail routing.
Test the affected pages, forms, checkout, login, SSL, redirects, and mobile views so the fix is real for visitors, not just visible in admin.
Provide plain-English notes and recommend maintenance, hosting, backups, monitoring, or security hardening only where it directly reduces repeat risk.
Who does the work
Metro Vancouver IT is a small Burnaby-based shop, not a ticket queue. The person who triages your site is the person who repairs it and writes your notes — no handoffs to a call centre, no offshore night shift guessing at your host.
CMS, stores, and platforms we repair
WordPress
Drupal
Joomla
Sitefinity
WooCommerce
Shopify
Magento
BigCommerce
PrestaShop
Squarespace
Wix
PHP
Laravel
Node.js
Azure
AWS
Linux
Windows
Related services
Ongoing updates, monitoring, and rapid fixes.
Learn moreMalware removal, blacklist reconsideration, and post-incident hardening.
WordPress malware removalOlder PHP, databases, and custom CMS troubleshooting.
Learn moreSitefinity troubleshooting, export, and migration planning.
Learn moreThe short list of failures we look at first, and the first-15-minutes checklist.
Learn moreFAQ
Tell us the URL, what broke, and what access you have. Most repairs total $180–$270 — 2–3 hours at $90 CAD/hour — and we confirm an estimate before billable work starts. WordPress, Drupal, Joomla, Shopify, WooCommerce, Magento, or any host.
Contact
Include the website URL, the exact symptom, when it started, and what access you have. Urgent requests are triaged the same business day when received during Pacific Time business hours.
Site down right now?
Contact
Tell us what you need help with and we will reply with clear next steps.
