Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

AS9316 · 0 seconds ago

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS9316"

JSON Docs

Warning: AS9316 (DACOM-PUBNETPLUS-AS-KR-KR) announces 17 IPv4 and 0 IPv6 prefixes. 3 warnings

AS page	AS9316
Holder	DACOM-PUBNETPLUS-AS-KR-KR - DACOM-PUBNETPLUS
Allocation	APNIC, South Korea (KR), allocated 1998-06-03
Prefixes (IPv4 / IPv6)	17 / 0
RPKI valid	0% (0 / 17)
Upstreams and peers	1

What to fix

Warning

No IPv6 prefixes announced.

Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

Open in ASN & BGP prefix lookup

Warning

10 of 17 announced prefixes have no ROA (RPKI not found): 58.29.0.0/16, 61.108.0.0/16, 112.76.0.0/15, 117.110.0.0/15, 122.153.0.0/16 (+5).

Without a ROA, networks cannot tell your routes from a hijack.

Fix: Create a ROA for each at your RIR portal, with origin AS9316 and a max length equal to the prefix length:

58.29.0.0/16 AS9316 max-length /16
61.108.0.0/16 AS9316 max-length /16
112.76.0.0/15 AS9316 max-length /15
117.110.0.0/15 AS9316 max-length /15
122.153.0.0/16 AS9316 max-length /16
122.203.0.0/16 AS9316 max-length /16
125.240.0.0/13 AS9316 max-length /13
125.248.0.0/14 AS9316 max-length /14
180.80.0.0/14 AS9316 max-length /14
210.220.0.0/19 AS9316 max-length /19

Open in RPKI / ROA validator Guide

Warning

PeeringDB did not answer: HTTP 404

Fix: Try again in a minute.

Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.

Pass: AS9316 announces 17 IPv4 and 0 IPv6 prefixes.
Warning: No IPv6 prefixes announced.
Warning: 10 of 17 announced prefixes have no ROA (RPKI not found): 58.29.0.0/16, 61.108.0.0/16, 112.76.0.0/15, 117.110.0.0/15, 122.153.0.0/16 (+5).
Info: The RPKI state of 7 prefixes was not looked up (no ROA of AS9316 covers them; only the first 10 are checked).
Pass: Every announced prefix has an IRR route object.
Info: One upstream or peer seen (AS3786): an outage there takes the whole network off the internet.

Holder	DACOM-PUBNETPLUS-AS-KR-KR - DACOM-PUBNETPLUS
IPv4 prefixes	17
IPv6 prefixes	0
RPKI	10 not found · 7 not looked up
Downstream networks	0

Routes to fix

Prefix	RPKI
58.29.0.0/16	No ROA
61.108.0.0/16	No ROA
112.76.0.0/15	No ROA
117.110.0.0/15	No ROA
122.153.0.0/16	No ROA
122.203.0.0/16	No ROA
125.240.0.0/13	No ROA
125.248.0.0/14	No ROA
180.80.0.0/14	No ROA
210.220.0.0/19	No ROA

Upstreams and peers seen to the left 1

AS3786 LG Uplus

Announced prefixes 17

58.29.0.0/16 61.108.0.0/16 112.76.0.0/15 117.110.0.0/15 122.153.0.0/16 122.203.0.0/16 125.240.0.0/13 125.248.0.0/14 180.80.0.0/14 210.220.0.0/19 211.35.0.0/18 211.42.0.0/17 211.61.0.0/18 211.112.128.0/17 211.173.0.0/17 211.241.0.0/17 220.65.0.0/16

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup

Registration Found at rdap.apnic.net.

Pass: Found at rdap.apnic.net.

Name	DACOM-PUBNETPLUS-AS-KR-KR
Handle	AS9316
Range	AS9316
Country	KR
Status	active
Abuse contact	hostmaster@nic.or.kr

Allocation

Registry (RIR)	APNIC
Country	South Korea (KR)
Delegated on	1998-06-03
Status	Allocated
Delegated range	AS9316 – AS9323

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts

Role	Name	Email
technical	AS Manager	ipadm@lguplus.co.kr
administrative	AS Manager	ipadm@lguplus.co.kr
abuse	IRT-KRNIC-KR	hostmaster@nic.or.kr

Source: https://rdap.apnic.net/autnum/9316. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup

PeeringDB PeeringDB did not answer: HTTP 404

Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup