Skip to main content

AS198983

TornadoDatacenter

Customer assignment ASN

Registry

Authoritative registration data

AS number
198983
Name
TornadoDatacenter
Organisation
Customer assignment ASN
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

2

Total announced

20

Announced prefixes

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

Prefixes announced by AS198983
104.194.128.0/22 IPv4 /22 not checked
45.61.152.0/22 IPv4 /22 not checked
104.194.140.0/24 IPv4 /24 not checked
104.194.141.0/24 IPv4 /24 not checked
104.194.142.0/24 IPv4 /24 not checked
104.194.143.0/24 IPv4 /24 not checked
104.194.144.0/24 IPv4 /24 not checked
104.194.145.0/24 IPv4 /24 not checked
104.194.146.0/24 IPv4 /24 not checked
104.194.147.0/24 IPv4 /24 not checked
104.194.148.0/24 IPv4 /24 not checked
104.194.149.0/24 IPv4 /24 not checked
104.194.150.0/24 IPv4 /24 not checked
104.194.151.0/24 IPv4 /24 not checked
153.75.88.0/24 IPv4 /24 not checked
160.20.145.0/24 IPv4 /24 not checked
167.88.162.0/24 IPv4 /24 not checked
172.86.124.0/24 IPv4 /24 not checked
2602:fa59:1::/48 IPv6 /48 not checked
2a0e:b540:ffa1::/48 IPv6 /48 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 AS198983 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS198983 in AS paths

Observed upstreams
Families
AS25369 BANDWIDTH-AS 363 4,925
v4 v6
AS30823 AUROLOGIC 357 541
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS198983 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.