Skip to main content

AS212591

PLTFRMS

Registry

Authoritative registration data

AS number
212591
Name
PLTFRMS
Organisation
PLTFRMS
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS212591
31.13.225.0/24 IPv4 /24 not checked
5.44.251.0/24 IPv4 /24 not checked
2001:67c:590::/48 IPv6 /48 not checked
2a0e:fd45:2f40::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS212591
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
BGP.Exchange - Amsterdam 1,000 Mbps IPv6
BGP.Exchange - Barcelona 1,000 Mbps IPv6
BGP.Exchange - Dusseldorf 1,000 Mbps IPv6
BGP.Exchange - Frankfurt 1,000 Mbps IPv6
BGP.Exchange - Fremont 1,000 Mbps IPv6
BGP.Exchange - Hong Kong 1,000 Mbps IPv6
BGP.Exchange - Kansas 1,000 Mbps IPv6
BGP.Exchange - London 1,000 Mbps IPv6
BGP.Exchange - Zurich 1,000 Mbps IPv6
ERA-IX Amsterdam 10,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
LSIX: Main 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS212591 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

34 networks seen before AS212591 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212591 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

64 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.