Skip to main content

AS51001

cielo

CIELO SRL

Registry

Authoritative registration data

AS number
51001
Name
cielo
Organisation
CIELO SRL
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS51001
185.158.236.0/24 IPv4 /24 not checked
185.158.237.0/24 IPv4 /24 not checked
185.158.238.0/24 IPv4 /24 not checked
185.158.239.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 AS51001
Address families
MIX-IT 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS51001 in AS paths

Observed upstreams
Families
AS6762 SEABONE-NET 160 772
v4
AS9002 RETN-AS 32 172
v4
AS6939 HURRICANE 28 120
v4
AS8218 NEO-ASN 6 56
v4
AS5405 INTERDOTLINK 7 36
v4
AS14840 ASN14840 2 20
v4
AS4455 BSO 2 12
v4
AS24961 MYLOC-AS 2 8
v4
AS6204 1 4
v4
AS9009 M247 1 4
v4
AS31543 MYNET-AS 1 4
v4
AS137409 GSLNETWORKS-AS-AP 1 4
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS51001 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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