Skip to main content

AS201900

OLGroupe

EAGLE FOOTBALL GROUP SA

Registry

Authoritative registration data

AS number
201900
Name
OLGroupe
Organisation
EAGLE FOOTBALL GROUP SA
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS201900
185.78.80.0/22 IPv4 /22 not checked
185.78.80.0/24 IPv4 /24 not checked
185.78.81.0/24 IPv4 /24 not checked
185.78.82.0/24 IPv4 /24 not checked
185.78.83.0/24 IPv4 /24 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 AS201900
Address families
France-IX AURA: lyonix-peering 2,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 AS201900 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS201900 in AS paths

Observed upstreams
Families
AS39180 LASOTEL 226 1,371
v4
AS12670 56 154
v4
AS6939 HURRICANE 28 145
v4
AS34019 HIVANE 4 30
v4
AS29075 2 10
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS201900 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS2027 MilkyWan 1 5
v4
AS56987 AS-ABACLOUDA 1 5
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.