Skip to main content

AS201933

AS4NET

** Transit Peerings IPv4 **

Registry

Authoritative registration data

AS number
201933
Name
AS4NET
Organisation
** Transit Peerings IPv4 **
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 AS201933
91.193.116.0/22 IPv4 /22 not checked
80.247.222.0/23 IPv4 /23 not checked
213.193.250.0/24 IPv4 /24 not checked
45.90.42.0/24 IPv4 /24 not checked
2a06:40c0::/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 AS201933
Address families
LINX LON1: Main 10,000 Mbps IPv4 · IPv6
LINX LON2 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 AS201933 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

19 networks seen before AS201933 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 818 2,146
v4 v6
AS3223 VOXILITY 261 360
v4
AS3356 LEVEL3 109 229
v4 v6
AS34549 MEER-AS 17 31
v4 v6
AS25091 IP-Max 8 30
v4 v6
AS35280 F5 11 23
v4 v6
AS48362 TKSWF-AS 2 20
v4 v6
AS5405 INTERDOTLINK 8 16
v4 v6
AS29075 IELO 9 15
v4 v6
AS34177 CELESTE-AS 8 15
v4 v6
AS39351 ESAB-AS 8 14
v4
AS9044 SOLNET 4 14
v4
AS9002 RETN-AS 4 8
v6
AS60171 AFRIX-AS 3 5
v4 v6
AS37100 ORG-SL75-AFRINIC 3 4
v4
AS37282 ORG-MCC1-AFRINIC 3 4
v4
AS37468 ORG-AC4-AFRINIC 3 4
v4
AS4455 BSO 2 4
v4
AS6204 1 1
v4

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS201933 in AS paths

Observed downstreams
Families
AS207673 281 383
v4
AS212797 280 382
v4
AS199710 PERFORM-AS 261 360
v4
AS43525 210 287
v4

No rows match “”.

Showing of

Uncertain adjacencies

32 adjacencies that may be an artefact of collector peering

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.