Skip to main content

AS52092

ALFSERVIS-AS

v4

Registry

Authoritative registration data

AS number
52092
Name
ALFSERVIS-AS
Organisation
v4
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS52092
46.149.112.0/20 IPv4 /20 not checked
91.227.134.0/23 IPv4 /23 not checked
2001:67c:3b4::/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 AS52092
Address families
NIX.CZ: Public peering VLAN 1,000 Mbps IPv4 · IPv6
Peering.cz 200,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 AS52092 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS52092 in AS paths

Observed upstreams
Families
AS39392 SuperNetwork 159 368
v4 v6
AS6939 HURRICANE 43 50
v6
AS8218 NEO-ASN 5 14
v4 v6
AS1764 NEXTLAYER-AS 3 12
v4 v6
AS14840 ASN14840 2 4
v6
AS4455 BSO 1 2
v4
AS6204 ZET-NET 1 2
v4
AS6663 TTI-NET 1 2
v4
AS13194 BITE 1 2
v4
AS20562 OPEN-PEERING-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS52092 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4 v6
AS47692 NESSUS 1 6
v4 v6
AS51184 FONIRA 1 6
v4 v6
AS29504 LBCFREE 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6
AS40994 Alwyzon 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS59890 Kabel-TV-Lampert 1 3
v4 v6
AS35369 LINZAG-TELEKOM-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.