Skip to main content

AS203062

ALEXANDRE-ROUX-ASRINFOPRO

Alexandre Roux trading as ASR INFOPRO

Registry

Authoritative registration data

AS number
203062
Name
ALEXANDRE-ROUX-ASRINFOPRO
Organisation
Alexandre Roux trading as ASR INFOPRO
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

27

Total announced

29

Announced prefixes

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

Prefixes announced by AS203062
217.9.10.0/24 IPv4 /24 not checked
23.138.204.0/24 IPv4 /24 not checked
2a01:e286:8000::/33 IPv6 /33 RPKI valid
2a06:2c81:8000::/33 IPv6 /33 RPKI valid
2a06:2c82:8000::/33 IPv6 /33 RPKI valid
2a06:2c83::/33 IPv6 /33 not checked
2602:f650::/36 IPv6 /36 not checked
2a01:e286:1000::/36 IPv6 /36 not checked
2a01:e286::/36 IPv6 /36 not checked
2a06:2c80:1000::/36 IPv6 /36 RPKI valid
2a06:2c80::/36 IPv6 /36 not checked
2a06:2c84:1000::/36 IPv6 /36 not checked
2a06:2c84::/36 IPv6 /36 not checked
2a0b:4e07:8000::/36 IPv6 /36 not checked
2a0b:4e07:9000::/36 IPv6 /36 RPKI valid
2a01:e286:2000::/37 IPv6 /37 RPKI valid
2a01:e286:2800::/37 IPv6 /37 RPKI valid
2a01:e286:3000::/37 IPv6 /37 RPKI valid
2a06:2c84:2000::/37 IPv6 /37 RPKI valid
2a06:2c84:2800::/37 IPv6 /37 not checked
2a06:2c84:3000::/37 IPv6 /37 RPKI valid
2a0b:4e07:a000::/37 IPv6 /37 not checked
2a0b:4e07:a800::/37 IPv6 /37 not checked
2a0b:4e07:b000::/37 IPv6 /37 not checked
2602:f650::/40 IPv6 /40 not checked
2a0c:9a40:9100::/40 IPv6 /40 RPKI valid
2a06:a005:1d40::/44 IPv6 /44 not checked
2a0b:4e07:77f0::/44 IPv6 /44 RPKI valid
2a06:2c80:b::/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 AS203062
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv6
ERA-IX Amsterdam 10,000 Mbps IPv6
FREMIX 1,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
IXP FI HEL: Finland 1,000 Mbps IPv6
IXP UK LON: United Kingdom 1,000 Mbps IPv6
IXP US FRE: Main 1,000 Mbps IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LONAP: LON0 1,000 Mbps IPv4 · IPv6
ONIX 1,000 Mbps IPv4 · IPv6
PeersIX Amsterdam 1,000 Mbps IPv6
ixFabric - Amsterdam 1,000 Mbps IPv6
ixFabric - Dusseldorf 1,000 Mbps IPv6
ixFabric - Frankfurt 1,000 Mbps IPv6
ixFabric - Fremont 1,000 Mbps IPv6
ixFabric - Paris 1,000 Mbps IPv6
ixFabric - Zurich 1,000 Mbps IPv6
nine 400,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 AS203062 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS203062 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 231 7,540
v4 v6
AS47160 MOJI 295 1,707
v4 v6
AS2027 MilkyWan 271 397
v4 v6
AS214757 Jakub-Krsa 74 203
v6
AS25091 IP-Max 3 95
v4 v6
AS34927 iFog-GmbH 27 47
v4 v6
AS215596 Kissgroup 1 28
v4 v6
AS5405 INTERDOTLINK 5 11
v4 v6
AS1103 SURFNET-NL 2 8
v4 v6
AS8298 IPNG 2 8
v4 v6
AS39351 ESAB-AS 2 8
v4 v6
AS34549 MEER-AS 4 7
v4 v6
AS11967 HOP179 2 6
v6
AS14840 ASN14840 2 5
v4
AS50629 LWLCOM 2 5
v4 v6
AS50304 BLIX 2 4
v6
AS61049 EXASCALE 2 4
v4
AS401753 BIXCE 1 3
v4 v6
AS6204 ZET-NET 1 2
v4
AS6696 VERIXI 1 2
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203062 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

29 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.