Updated January 14, 2024: The TTC has implemented auto-forwarding of URLs that point to the azureedge site to cdn.ttc.ca. Links to azureedge should now work properly. However, links to reports created on the old TTC site will fail because the URLs have completely changed and auto-forwarding is not possible.

Across various sites including this one, the City of Toronto, and the TTC’s own site, there are many links to reports on the TTC site.

The last time the TTC reorganized its site, the URL for all reports changed to a complex string that began with:

ttc-cdn.azureedge.net/

This has now changed to

cdn.ttc.ca/

If you click a link and it fails on a “server not found” error for “azureedge.net”, you will have to manually change the URL to the correct server name. (Do this carefully so as not to disturb the rest of the very long URL for reports on the site.)

At least the remainder of the URL still works. The last time the TTC revised its site, complete file names changed and finding reports required tracking down their revised locations. This also broke all of the results from search engines.

The TTC appears to have updated links within its own site, but not within files such as Board reports that refer to each other. This is a recent change. Reports within the September 26, 2023 Board meeting agenda include links to the old server name and these fail.

Why this was implemented without an auto-redirect from the old name to the new one is a mystery. This is yet another example of a change that makes the TTC’s site less useable. This is not just a question for a blogger like me who routinely links TTC reports, but for all agencies including the TTC and City who embed links to TTC reports in their documents.

I have sent a query to the TTC asking if this problem will be fixed, and will update this article when I hear back.