ixreport

R09TELECOM

AS219310

EMIRASLAN EMIRASLANOV, homelab network

PeeringDB Follow changes
1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
–Peering policy
1Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with R09TELECOM? · Where should R09TELECOM peer next?

PeeringDB fix list Printable page

One thing to fix in R09TELECOM's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 21:56 UTC.

Make the changes on R09TELECOM'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 R09TELECOM's PeeringDB record. Add one entry per connection with these values.

  1. United States EVIX Fremont, United States · PeeringDB 2274From its IX-F export
    IPv4–
    IPv62602:fed2:fff:ffff:6::126
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

This chart fills in as daily counts build up; the first was Oct 8, 2026.

Exchanges
United States EVIX Fremont, United States 2602:fed2:fff:ffff:6::126 1G Yes Not in PeeringDB

R09TELECOM lists no facilities in PeeringDB.

Recent changes Search them

  • Oct 8, 2026 [IXF] AS219310 R09TELECOM added to EVIX