AS207351 Transroute Telecom second AS
AS207351 is operated by Transroute Telecom second AS and registered with RIPE NCC (RU) since 2020-02-21.
It is not announcing any prefixes right now.
PeeringDB lists it as an NSP network at 1 internet exchange and 1 facility. Its peering policy is open.
| Name | Transroute Telecom second AS |
|---|---|
| Registry (RIR) | RIPE NCC |
| Country | Russia (RU) |
| Delegated on | 2020-02-21 |
| Network type | NSP, Europe |
| Peering policy | Open |
| IRR as-set | AS-TRANSROUTE-2 |
| Prefixes (IPv4 / IPv6) | 0 / 0 |
| Website | transroute.net |
Routing health
- AS207351 is not announcing anything right now.
For every check with the fix (IRR route objects, the RPKI state of each route, reverse DNS and the registration), run the full network report.
Upstreams and peers 10
The networks RIPE RIS sees next to AS207351 in BGP paths, the most visible first.
Peering
Peering policy: Open. Suggested max-prefix limits: 30,000 IPv4, 5,000 IPv6. PeeringDB record
| Exchange | Ports | Speed | Route server |
|---|---|---|---|
| Eurasia Peering IX: Peering LAN | 1 | 100G | Yes |
| Facility | City | Country |
|---|---|---|
| Moscow M9 | Moscow | RU |
More about AS207351
Sources: RIR delegation data and PeeringDB (updated daily); routing from RIPEstat (RIPE NCC RIS and RPKI), refreshed daily. Routing data from 2026-11-14 05:22 UTC. The country is where the AS number was registered, not necessarily where the network operates.