Skip to main content

AS199516

PACKNET-AS

--

Registry

Authoritative registration data

AS number
199516
Name
PACKNET-AS
Organisation
--
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS199516
185.13.80.0/24 IPv4 /24 not checked
185.13.81.0/24 IPv4 /24 not checked
185.13.82.0/24 IPv4 /24 not checked
185.13.83.0/24 IPv4 /24 not checked
2a02:f380::/29 IPv6 /29 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 AS199516
Address families
LINX Manchester 1,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 AS199516 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS199516 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 259 1,615
v4 v6
AS174 COGENT-174 43 208
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199516 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 45
v4 v6
AS3170 VELOXSERV 1 5
v4 v6
AS36236 NETACTUATE 1 5
v4 v6
AS48070 DSM 1 5
v4 v6
AS13237 LAMBDANET-AS 1 4
v4
AS28792 PUBLIC-INTERNET 1 4
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.