Skip to main content

AS201699

LEVELSYS

LEVEL SYS SAS

Registry

Authoritative registration data

AS number
201699
Name
LEVELSYS
Organisation
LEVEL SYS SAS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS201699
150.251.248.0/22 IPv4 /22 not checked
185.187.164.0/22 IPv4 /22 not checked
185.208.140.0/22 IPv4 /22 not checked
185.219.212.0/22 IPv4 /22 not checked
185.58.8.0/22 IPv4 /22 not checked
31.42.116.0/22 IPv4 /22 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS201699 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS201699 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 229 1,439
v4
AS6461 ZAYO-6461 35 192
v4
AS1299 TWELVE99 28 33
v4
AS34019 HIVANE 2 15
v4
AS5405 INTERDOTLINK 2 10
v4
AS6057 6057 2 10
v4
AS8298 IPNG 2 10
v4
AS29075 IELO 2 10
v4
AS34177 CELESTE-AS 2 10
v4
AS35280 F5 2 6
v4
AS6758 AS6758 1 5
v4
AS39351 ESAB-AS 1 5
v4
AS60171 AFRIX-AS 1 5
v4
AS56911 ASN-WARIAN 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS201699 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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