StatusCake

Canada’s immigration website crashes due to traffic surge

statuscake

The contentious US presidential election is over and contrary to the expectations of most people, Donald Trump won. Canada was among the first to experience the effects of this decision. About two hours after polls closed in eastern US states and it became apparent that Trump would win, Canada’s main immigration website crashed.

There had been many tongue-in-cheek articles (and a few serious ones) in US newspapers and online discussing how large numbers of Americans would move to Canada if Trump won the election. Also, a Canadian radio host impishly launched a website in February pitching Cape Breton Island, located off Canada’s east coast, as an ideal location for American refugees to make their new home. As it turned out, there was quite a bit of interest in immigration on election night.

Traffic on the Citizenship and Immigration Canada website surged from a typical 17,000 visitors to over 200,000 visitors on election night at the time of the crash, with about 50% of the traffic coming from the US. After the crash, visitors to the site saw a message stating, “there is a problem with the resource you are looking for, and it cannot be displayed” and they could not access any content.

Canada’s immigration website was not the only one experiencing an increase in traffic on election night. The Telegraph reported that Google experienced a significant increase in searches for terms like “how to emigrate to Canada” and “emigrate,” and the BBC reported that Immigration New Zealand (INZ) experienced a 2,500% increase in traffic on election day.

Prepare your site to receive heavy traffic

As the recent crash of Canada’s immigration website shows, unforeseen events can cause a surge in traffic, and sometimes increased traffic can do more harm than good. A brief website outage may usually not hurt you very much, but it can tarnish your image badly if it happens during a time of peak traffic. Fortunately, there are a few things you can do to help prevent your site from crashing if you do receive an unexpectedly large increase in traffic.

Google’s Webmaster Central Blog suggests several best practices you can implement to prepare your site for a traffic surge. Consider preparing a lightweight version of your site that you can switch to if you begin to experience a spike in traffic. Hosting forms on a third-party server can help your server cope with increased traffic loads.

Also, optimize your image files by compressing them and having them automatically adjust to the appropriate size for display on mobile devices. Consider using your server’s cache for static content, as this will help keep your server’s capacity available in high-traffic situations.

You never know when the unexpected will happen, so consider using a website monitoring service that will promptly notify you if your site goes down. The sooner you are aware of a problem, the sooner you can act to fix it.

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.