Skip to main content

AS12464

PW-NET

Warsaw University of Technology

Registry

Authoritative registration data

AS number
12464
Name
PW-NET
Organisation
Warsaw University of Technology
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS12464
194.29.128.0/19 IPv4 /19 not checked
194.29.160.0/20 IPv4 /20 not checked
194.29.176.0/22 IPv4 /22 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS12464 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS12464 in AS paths

Observed upstreams
Families
AS1887 184 711
v4
AS29314 VECTRANET-AS 46 180
v4
AS6939 HURRICANE 30 105
v4
AS24115 ASN-EQIX-MLPE 6 18
v4
AS137409 GSLNETWORKS-AS-AP 3 12
v4
AS8664 ICM-PUB 2 6
v4
AS9009 M247 1 3
v4
AS13194 BITE 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS12464 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 12
v4
AS49544 i3Dnet 1 6
v4
AS36236 NETACTUATE 1 3
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.