Skip to main content

AS206660

sphere-telecom

Sphere Telecom SARL

Registry

Authoritative registration data

AS number
206660
Name
sphere-telecom
Organisation
Sphere Telecom SARL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS206660
149.13.164.0/22 IPv4 /22 RPKI not found
87.236.34.0/24 IPv4 /24 not checked
2a09:ea40::/29 IPv6 /29 RPKI not found

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 AS206660
Address families
Lillix — 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 AS206660 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS206660 in AS paths

Observed upstreams
Families
AS29075 IELO 76 169
v4
AS174 COGENT-174 52 117
v4
AS6939 HURRICANE 57 84
v4 v6
AS9002 RETN-AS 11 15
v6
AS25091 IP-Max 3 6
v4 v6
AS8218 NEO-ASN 2 3
v6
AS39351 ESAB-AS 1 3
v4 v6
AS5405 INTERDOTLINK 1 2
v4
AS34177 CELESTE-AS 1 2
v4
AS33891 CORE-BACKBONE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS206660 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 11
v4 v6
AS35280 F5 1 4
v4 v6
AS12779 ITGATE 1 3
v4 v6
AS34019 HIVANE 1 3
v4 v6
AS34288 AS34288 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS50628 Leonix-Telecom 1 3
v4 v6
AS204092 GRIFON 1 3
v4 v6
AS13237 LAMBDANET-AS 1 2
v4
AS15547 NETPLUS 1 2
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.