Skip to main content

AS8819

PL-METROINTERNET

Metro Internet Sp. z o.o.

Registry

Authoritative registration data

AS number
8819
Name
PL-METROINTERNET
Organisation
Metro Internet Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS8819
46.227.104.0/21 IPv4 /21 not checked
83.142.192.0/21 IPv4 /21 not checked
91.189.24.0/21 IPv4 /21 not checked
185.188.68.0/22 IPv4 /22 not checked
2a0e:6180::/29 IPv6 /29 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 AS8819
Address families
EPIX.Katowice 10,000 Mbps IPv4 · IPv6
EPIX.Warszawa 40,000 Mbps IPv4 · IPv6
Equinix Warsaw 10,000 Mbps IPv4 · IPv6
TPIX PL 10,000 Mbps IPv4 · 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 AS8819 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS8819 in AS paths

Observed upstreams
Families
AS62081 160 882
v4 v6
AS5617 155 633
v4 v6
AS6939 HURRICANE 88 117
v6
AS50607 57 110
v4 v6
AS24115 ASN-EQIX-MLPE 8 35
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 15
v4 v6
AS6204 1 4
v4
AS35320 1 4
v4
AS29632 NASSIST-AS 3 3
v6
AS39249 1 1
v6
AS201054 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS8819 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 45
v4 v6
AS49544 i3Dnet 1 10
v4 v6
AS36236 NETACTUATE 1 5
v4 v6
AS28917 1 4
v4

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.