Skip to main content

AS199918

WARPNET

Wilton Arthur Poth

Registry

Authoritative registration data

AS number
199918
Name
WARPNET
Organisation
Wilton Arthur Poth
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

3

Total announced

5

Announced prefixes

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

Prefixes announced by AS199918
164.138.200.0/24 IPv4 /24 RPKI valid
196.1.104.0/24 IPv4 /24 RPKI valid
2a04:5a80::/31 IPv6 /31 RPKI valid
2001:67c:34::/48 IPv6 /48 not checked
2a04:5a80:ac::/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

Internet Exchange memberships listed for AS199918
Address families
FogIXP 1,000 Mbps 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 AS199918 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS199918 in AS paths

Observed upstreams
Families
AS20473 AS-VULTR 181 706
v4 v6
AS34927 iFog-GmbH 35 112
v4 v6
AS14840 ASN14840 2 8
v6
AS39351 ESAB-AS 1 2
v6
AS205794 RTTW-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199918 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
AS58299 OPENFACTORY-AS 1 2
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.