Skip to main content

AS41107

backbone-connect

Backbone Connect Limited

Registry

Authoritative registration data

AS number
41107
Name
backbone-connect
Organisation
Backbone Connect Limited
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

15

IPv6 prefixes

1

Total announced

16

Announced prefixes

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

Prefixes announced by AS41107
178.255.64.0/21 IPv4 /21 not checked
5.133.240.0/21 IPv4 /21 not checked
91.108.160.0/21 IPv4 /21 not checked
159.253.160.0/22 IPv4 /22 not checked
178.255.68.0/22 IPv4 /22 not checked
185.31.152.0/22 IPv4 /22 not checked
185.38.112.0/22 IPv4 /22 not checked
193.24.252.0/22 IPv4 /22 not checked
195.60.208.0/22 IPv4 /22 not checked
217.61.228.0/22 IPv4 /22 not checked
80.208.216.0/22 IPv4 /22 not checked
80.208.222.0/23 IPv4 /23 not checked
217.61.228.0/24 IPv4 /24 not checked
217.61.229.0/24 IPv4 /24 not checked
80.208.220.0/24 IPv4 /24 not checked
2a03:bc40::/29 IPv6 /29 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 AS41107
Address families
LINX LON1: Main 20,000 Mbps IPv4 · IPv6
LINX LON2 10,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 AS41107 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

40 networks seen before AS41107 in AS paths

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS41107 in AS paths

Observed downstreams
Families
AS212446 256 335
v4
AS51553 257 333
v4
AS52024 27 42
v4
AS34654 19 23
v4

No rows match “”.

Showing of

Uncertain adjacencies

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