Skip to main content

AS64415

CONNECTBIT-AS

****************************************

Registry

Authoritative registration data

AS number
64415
Name
CONNECTBIT-AS
Organisation
****************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS64415
185.100.248.0/24 IPv4 /24 not checked
185.100.249.0/24 IPv4 /24 not checked
185.100.250.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 AS64415
Address families
LONAP: LON0 1,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 AS64415 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS64415 in AS paths

Observed upstreams
Families
AS174 COGENT-174 80 282
v4
AS39537 HNS 28 90
v4
AS6939 HURRICANE 12 36
v4
AS33891 CORE-BACKBONE 5 21
v4
AS8218 NEO-ASN 3 12
v4
AS45014 NCONNECT 3 12
v4
AS14840 ASN14840 2 12
v4
AS6204 ZET-NET 1 3
v4
AS9009 M247 1 3
v4
AS39351 ESAB-AS 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS64415 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 15
v4
AS34927 iFog-GmbH 1 3
v4
AS48185 team_blue 1 3
v4
AS49544 i3Dnet 1 3
v4
AS50300 CUSTDC 1 3
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.