Skip to main content

AS8890

UW-AS

Warsaw, Poland

Registry

Authoritative registration data

AS number
8890
Name
UW-AS
Organisation
Warsaw, Poland
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 AS8890
193.0.64.0/18 IPv4 /18 not checked
212.87.0.0/20 IPv4 /20 not checked
2001:6a0::/32 IPv6 /32 not checked
2001:6a0:4000::/34 IPv6 /34 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 AS8890
Address families
Equinix Warsaw 10,000 Mbps IPv4 · IPv6
TPIX PL 20,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 AS8890 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS8890 in AS paths

Observed upstreams
Families
AS29535 279 770
v4 v6
AS6939 HURRICANE 211 299
v6
AS43372 19 46
v4
AS8664 ICM-PUB 9 13
v6
AS6204 1 2
v4
AS201054 EPIX-PolMix 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS8890 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS28917 Fiord-AS 1 2
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.