ixreport

Timer

AS47626 · ArpNet

Timer Ltd.

11Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
11Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Timer? · Where should Timer peer next? · Compare Timer 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 Timer's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Timer's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 30G30G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

051015Oct 3, 2026Nov 19, 202611
Show as a table
DateExchanges
Nov 19, 202611
Nov 18, 202611
Nov 17, 202611
Nov 16, 202611
Nov 15, 202611
Nov 14, 202611
Nov 13, 202611
Nov 12, 202611
Nov 11, 202611
Nov 10, 202611
Nov 9, 202611
Nov 8, 202611
Nov 7, 202611
Nov 6, 202611
Nov 5, 202611
Nov 4, 202611
Nov 3, 202611
Nov 2, 202611
Nov 1, 202611
Oct 31, 202611
Oct 30, 202611
Oct 29, 202611
Oct 28, 202611
Oct 27, 202611
Oct 26, 202611
Oct 25, 202611
Oct 24, 202611
Oct 23, 202611
Oct 22, 202611
Oct 21, 202611
Oct 20, 202611
Oct 19, 202611
Oct 18, 202611
Oct 17, 202611
Oct 16, 202611
Oct 15, 202611
Oct 14, 202611
Oct 13, 202611
Oct 12, 202611
Oct 11, 202611
Oct 10, 202611
Oct 9, 202611
Oct 8, 202611
Oct 7, 202611
Oct 6, 202611
Oct 5, 202611
Oct 4, 202611
Oct 3, 202611

Map

Where Timer'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.

Exchanges

Total port capacity 370G across 11 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.68 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.213
178.18.226.146
2a03:5f80:4::225:213
2a03:5f80:4::226:146
2 × 30G Yes Both Speed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.208.229
195.208.210.229
20G Yes Both
Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia 193.232.140.36 10G Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.187.8 40G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.4 40G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.12.13 40G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.97 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.20 40G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.58 40G Yes PeeringDB
Russia Sea-IX Krasnodar, Russia 91.240.225.169 30G Yes PeeringDB

Exchanges in its buildings that it isn't on (4)

These exchanges have a switch in a facility where Timer lists itself in PeeringDB, but don't have Timer 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.

Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (1)

The buildings Timer lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 5 of 9