docs: re-verify Direct Connect facts as of 2026-10-12

[kanywst]

Monthly freshness check (closes #2).

Re-verified against AWS sources on 2026-10-12:

• Pricing: port-hours (incl. Japan), DTO matrix, flat-rate example ($10.96/h 10G Tier 1 at Equinix DC2) unchanged (pricing page, flat-rate page, Price List API version 20261005164936).
• Quotas: unchanged (limits.html).
• New launches 2026-09-30 to 2026-10-12: none (User Guide document history, What's New feed through 2026-10-09).
• Locations and speeds: 400G list and MACsec examples unchanged. Added the Equinix MU1 Munich end-of-support notice from the locations page to the timeline.
• SLA: unchanged (last updated 2026-07-24).

Bumps the as-of dates (UI, PRICES_AS_OF, docs). docs/13 keeps 2026-09-30 since that is the research date.

Not added: hosted 50G SKUs appear in the Price List (Osaka 2, Lisbon) but are not on the public pricing page or in What's New.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 41f4d831-d5e5-4ec0-9e8d-91577a6fdeec

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

The Equinix MU1 Munich claim (no new connections after July 1, 2026, end of support July 2027) is cited only to the locations page. I couldn't fetch that page, so I couldn't check it. Please confirm the dates there and add a document history or What's New link if one exists. The sentence also says "both with end of support in July 2027", but the source list gives no second source for MU1. Also check the Shenzhen wording: "after 2026-06-30" and "after July 1, 2026" describe the same cutoff, so the parenthetical reads as a conflict when it may not be one.

Nothing in docs/ or src/content/ mentions MU1 or the Shenzhen wind-down. If the site's location views or the Japanese content cover locations, they may need the same note.

[claude]

Review of the 2026-10-12 re-verification.

The EN/JA date bumps are consistent. These all moved from 2026-09-30 to 2026-10-12: README.md, README.ja.md, src/content/ui.ts (both languages), src/lib/pricing.ts (PRICES_AS_OF and the comment), and the docs headers. The docs/13-why-dx-is-hard.md date is a research date, so leaving it alone is correct.

One finding, inline on docs/12-timeline.md:82: the new Equinix MU1 Munich end-of-support claim rests on a single source, the locations page. I couldn't fetch that page, so the dates are unverified here. Please confirm them against the page before merge.

The PR also says prices were re-taken on 2026-10-12. I did not check the live pricing page, so I can't confirm that no prices changed.

[claude]

The MU1 Munich wind-down and the "July 1, 2026" cutoff are new factual claims, and I could not check them against the locations page from the review environment. The sentence cites the locations page for both dates, but the page is not listed in the docs' other sources for these facts and nothing here quotes it. Please confirm that the page words it as "after July 1" and not "after June 30", and that it also gives July 2027 for MU1.

The sentence also gives two cutoffs for Shenzhen, "after July 1, 2026" and "after June 30, 2026". If AWS means the same day by both, a reader may take them as different days. Say plainly which one is the last day to order, or state that the two sources word it differently.

The footprint paragraph is where these are recorded, but the date bump to 2026-10-12 on every page claims a full re-verification. Only this paragraph changed substantively.

[claude]

The only substantive change is the location wind-down sentence in docs/12-timeline.md:82: it adds Equinix MU1 Munich and states the Shenzhen cutoff as July 1, 2026, while the document history says June 30, 2026. I could not fetch the AWS locations page from this environment, so I could not confirm either date or the July 2027 end of support. Please check them against the page before merging.

The other 16 files only move the "verified on" date from 2026-09-30 to 2026-10-12, and that date is consistent across EN, JA, docs/, src/content/ui.ts and src/lib/pricing.ts. The date bump claims every page and the pricing figures were re-checked on 2026-10-12. Nothing in the diff shows that, so confirm the prices and quotas were actually re-checked.

Nothing else needs flagging: there are no workflow, injection or EN/JA parity issues.

[kanywst]

Post-merge follow-up on the Claude review (both rounds):

• MU1 / Shenzhen dates: checked against https://aws.amazon.com/directconnect/locations/ on 2026-10-12. Both entries read verbatim "End of support July 2027. No new connections after July 1, 2026". The second commit (4166370) states them as the page gives them and keeps the document-history wording for Shenzhen ("after June 30, 2026") as a note, not a conflict. The page does not have a What's New post or a document-history entry for MU1.
• Evidence for the date bump: the PR description lists what was re-checked: the pricing page, the flat-rate page, Price List API version 20261005164936, limits.html, the User Guide document history, the What's New feed through 2026-10-09, the locations page and the SLA. Nothing changed, so the diff only moves the as-of dates.
• Site content: the location views do not cover wind-downs, so no UI or JA change is needed.