Skip to main content

AS12502

NEPUSTILNET-AS01

Rathausstr. 3

Registry

Authoritative registration data

AS number
12502
Name
NEPUSTILNET-AS01
Organisation
Rathausstr. 3
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

2

Total announced

8

Announced prefixes

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

Prefixes announced by AS12502
212.71.192.0/19 IPv4 /19 not checked
194.55.100.0/23 IPv4 /23 not checked
195.93.166.0/23 IPv4 /23 not checked
193.105.105.0/24 IPv4 /24 not checked
193.96.243.0/24 IPv4 /24 not checked
195.190.145.0/24 IPv4 /24 not checked
2001:14f8::/32 IPv6 /32 not checked
2001:67c:684::/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 AS12502
Address families
KleyReX: Peering LAN 1,000 Mbps IPv4 · IPv6
Stuttgart-IX: PeeringLAN 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 AS12502 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS12502 in AS paths

Observed upstreams
Families
AS5405 INTERDOTLINK 1,156 4,689
v4 v6
AS33843 NEPUSTILNET-AS02 206 683
v4 v6
AS1299 TWELVE99 97 644
v4 v6
AS33891 CORE-BACKBONE 4 14
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS12502 in AS paths

Observed downstreams
Families
AS203132 SySS 350 1,893
v4 v6
AS49499 ASIHKRT 182 484
v4
AS206394 CEGAT 233 433
v4 v6
AS43910 INTRA2NET-AS 270 346
v4
AS209846 swpforzheim 66 107
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS47147 AS-ANX 4 48
v4
AS553 BELWUE 5 19
v4 v6

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.