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
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.
StatusCake Team
Share this
More from StatusCake
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026