ixreport

Erline

AS47895 · R-Line

LTD "Erline"

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

Tools: Where can I peer with Erline? · Where should Erline peer next? · Compare Erline with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Erline's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Erline'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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:18 2a03:5f80:4::225:241
    Port speed differs2 × 100G100G
    • In the entry with IPv4 178.18.224.18: set IPv6 to 2a03:5f80:4::224:18 (now empty).
    • In the entry with IPv4 178.18.225.241: set IPv6 to 2a03:5f80:4::225:241 (now empty).

    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

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

Map

Where Erline'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 280G across 5 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.18
178.18.225.241
2 × 100G Yes Both IPv6 not in PeeringDBSpeed differs
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.187.42
31.44.187.76
2 × 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.52
193.27.37.253
2 × 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.14.135
185.0.14.147
2 × 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.85
185.1.153.164
2 × 10G Yes PeeringDB

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

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

Russia MSK-IX MoscowMoscow, Russia 638 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 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 Erline lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 3 of 9