Skip to main content

AS396969

STRADA-COMM

Strada Communications L.L.C.

Registry

Authoritative registration data

AS number
396969
Name
STRADA-COMM
Organisation
Strada Communications L.L.C.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS396969
144.34.96.0/20 IPv4 /20 not checked
170.203.56.0/21 IPv4 /21 not checked
147.92.60.0/22 IPv4 /22 not checked
2607:be40::/28 IPv6 /28 RPKI not found
2607:be40::/32 IPv6 /32 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 AS396969
Address families
QCIX: Main 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 AS396969 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS396969 in AS paths

Observed upstreams
Families
AS62943 AS62943-BLUEBIRD-NETWORK 200 768
v4
AS6939 HURRICANE 203 575
v6
AS11796 AIRSTREAMCOMM-NET 42 149
v4 v6
AS5056 AUREON-5056 18 40
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS396969 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS394414 AS394414 1 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.