Skip to main content

AS13845

ESTRUXTURE-AB-13845

eStruxture Data Centers Inc.

Registry

Authoritative registration data

AS number
13845
Name
ESTRUXTURE-AB-13845
Organisation
eStruxture Data Centers Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS13845
66.51.16.0/21 IPv4 /21 RPKI valid
69.165.88.0/21 IPv4 /21 not checked
148.66.252.0/22 IPv4 /22 RPKI valid
205.209.2.0/23 IPv4 /23 not checked
142.231.0.0/24 IPv4 /24 RPKI valid
148.66.241.0/24 IPv4 /24 RPKI valid
204.209.8.0/24 IPv4 /24 not checked
38.121.74.0/24 IPv4 /24 RPKI not found
66.51.18.0/24 IPv4 /24 not checked
66.51.20.0/24 IPv4 /24 RPKI valid
2600:3000:5100::/40 IPv6 /40 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 AS13845
Address families
YYCIX 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 AS13845 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS13845 in AS paths

Observed upstreams
Families
AS577 BACOM 449 1,665
v4
AS6327 SHAW 323 971
v4 v6
AS6939 HURRICANE 33 143
v4
AS394256 CLOUDSINGULARITY 2 9
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS13845 in AS paths

Observed downstreams
Families
AS18701 PPCO-US 160 501
v4
AS32121 32121 138 318
v4
AS4361 VERSATURE-NET2PHONE 143 166
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS852 ASN852 3 14
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.