Skip to main content

AS14619

AS-THERA-US

THERA NETWORKS

Registry

Authoritative registration data

AS number
14619
Name
AS-THERA-US
Organisation
THERA NETWORKS
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

2

Total announced

3

Announced prefixes

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

Prefixes announced by AS14619
23.129.4.0/24 IPv4 /24 not checked
2602:f7aa::/36 IPv6 /36 not checked
2602:f7aa::/40 IPv6 /40 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS14619 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS14619 in AS paths

Observed upstreams
Families
AS1031 PEER1-1031 480 686
v4 v6
AS53062 399 504
v4 v6
AS265137 102 150
v4 v6
AS33891 CORE-BACKBONE 15 23
v4 v6
AS61621 ASN61621 7 10
v6
AS3303 SWISSCOM 5 7
v4
AS18782 4 5
v4
AS24961 2 2
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS14619 in AS paths

Observed downstreams
Families
AS18782 522 688
v6

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 3 8
v4 v6
AS199524 GCORE 3 5
v4 v6
AS1828 UNITAS 1 1
v4
AS8455 1 1
v4
AS263152 1 1
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.