Skip to main content

AS210412

hampsteadfibre

EX Networks

Registry

Authoritative registration data

AS number
210412
Name
hampsteadfibre
Organisation
EX Networks
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 AS210412
45.150.57.0/24 IPv4 /24 RPKI valid
89.106.203.0/24 IPv4 /24 not checked
2a12:b380::/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 AS210412
Address families
LONAP: LON0 5,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 AS210412 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS210412 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 153 361
v4 v6
AS35266 EXN-AS 106 193
v4 v6
AS6939 HURRICANE 96 136
v4 v6
AS8218 NEO-ASN 10 27
v4 v6
AS14840 ASN14840 4 20
v4 v6
AS33891 CORE-BACKBONE 11 16
v4
AS22356 ASN22356 2 5
v4 v6
AS39351 ESAB-AS 2 5
v4 v6
AS4455 BSO 2 3
v4
AS6204 ZET-NET 2 3
v4
AS9009 M247 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS210412 in AS paths

Observed downstreams
Families
AS211289 JOSH 194 325
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 25
v4 v6
AS34927 iFog-GmbH 2 5
v4 v6
AS48185 team_blue 2 5
v4 v6
AS49544 i3Dnet 2 5
v4 v6
AS50300 CUSTDC 2 5
v4 v6

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.