Skip to main content

AS16101

ORDIPAT

Ordipat SAS

Registry

Authoritative registration data

AS number
16101
Name
ORDIPAT
Organisation
Ordipat SAS
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS16101
193.41.194.0/24 IPv4 /24 not checked
2001:67c:2b38::/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 AS16101
Address families
France-IX Paris 200 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 AS16101 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS16101 in AS paths

Observed upstreams
Families
AS8218 NEO-ASN 145 313
v4 v6
AS30781 JAGUAR-AS 115 186
v4 v6
AS6939 HURRICANE 61 85
v4 v6
AS9002 RETN-AS 6 11
v6
AS34019 HIVANE 3 9
v4 v6
AS20764 RASCOM-AS 4 6
v4 v6
AS35280 F5 2 4
v4 v6
AS39351 ESAB-AS 2 4
v4 v6
AS4455 BSO 1 2
v4 v6
AS6758 AS6758 1 2
v4 v6
AS60171 AFRIX-AS 1 2
v4 v6
AS7713 telkomnet-as-ap 1 1
v4
AS20766 GITOYEN-MAIN-AS 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS16101 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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