Skip to main content

AS199118

HPLS-AS

ORG-HPLS2-RIPE

Registry

Authoritative registration data

AS number
199118
Name
HPLS-AS
Organisation
ORG-HPLS2-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS199118
80.241.56.0/21 IPv4 /21 not checked
185.97.172.0/22 IPv4 /22 not checked
195.10.208.0/24 IPv4 /24 not checked
80.241.60.0/24 IPv4 /24 not checked
91.198.250.0/24 IPv4 /24 not checked
91.223.20.0/24 IPv4 /24 not checked
2001:67c:2050::/48 IPv6 /48 RPKI valid

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 AS199118
Address families
BCIX: BCIX Peering LAN 3,500 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 AS199118 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS199118 in AS paths

Observed upstreams
Families
AS20647 IPB 122 902
v4 v6
AS3356 LEVEL3 102 751
v4 v6
AS6939 HURRICANE 219 441
v4 v6
AS8218 NEO-ASN 6 93
v4 v6
AS13030 INIT7 5 47
v4 v6
AS33891 CORE-BACKBONE 5 42
v4
AS39351 ESAB-AS 2 14
v4 v6
AS6797 GLOBALCONNECT-NET 1 14
v4 v6
AS24961 MYLOC-AS 2 13
v4 v6
AS9002 RETN-AS 5 9
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199118 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 61
v4 v6
AS680 DFN 1 7
v4 v6
AS50629 LWLCOM 1 7
v4 v6
AS13237 LAMBDANET-AS 1 6
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.