Datablocks
AS25948 · Datablocks
1882914 Ontario Inc
Tools: Where can I peer with Datablocks? · Where should Datablocks peer next? · Compare Datablocks with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
One thing to fix in Datablocks's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.
Make the changes on Datablocks's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Datablocks's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.126.225.86 IPv6 2001:504:2f::2:5948:1 Speed Not published RS peer Not published
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
Map
Where Datablocks's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
These exchanges have a switch in a facility where Datablocks lists itself in PeeringDB, but don't have Datablocks as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| EVIXFremont, United States | 227 | |
| ONIXToronto, Canada | 207 | |
| FREMIXFremont, United States | 141 | |
| SFMIXSan Francisco, United States | 100 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| MegaIX TorontoToronto, Canada | 16 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| CANIX TorontoToronto, Canada | 10 | |
| Ninja-IX Bay AreaNorthern California, United States | 6 | |
| ixFabricGlobal, Australia | 2 |
Facilities (2)
The buildings Datablocks lists in PeeringDB, and how many of the exchanges in each it's on.
| Hurricane Electric Fremont 2Fremont | 1 of 12 | |
| Telehouse Toronto (151 Front St West)Toronto | 1 of 4 |