bgpreport

Network · data from 2026-11-12

AS38909 ARDION-AS-AP - ARLINE BERBA ESTRADA t/a ARDION LINE WEB DESIGN

Registry name: ARDION-AS-AP - ARLINE BERBA ESTRADA t/a ARDION LINE WEB DESIGN, PH · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
2No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS38909, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38909, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

203.160.185.0/24 Invalid: origin Other origin only 21 3%low visibility 16
118.88.8.0/21 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
103.6.96.0/22 No ROA Other IRR onlyRADB 669 99% 66

AS-SET

AS38909 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin203.160.185.0/24ROAs covering it name AS18233, not AS38909. If AS38909 should announce it, add a ROA for AS38909.21 of 673
Route object: none203.160.185.0/24Route objects for it name AS18233. Add a route object with origin AS38909 in the RIR database for the space.21 of 673
ROA: none118.88.8.0/21No ROA covers it. Add a ROA for AS38909, maxLength 21.671 of 673
Route object: RIR118.88.8.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.6.96.0/22No ROA covers it. Add a ROA for AS38909, maxLength 22.669 of 673
Route object: RIR103.6.96.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS38909 whose prefix no peer sees AS38909 announce. Many are kept on purpose (backup routes, space announced only in some places).

118.88.8.0/24NTTCOMNo ROA
118.88.9.0/24NTTCOMNo ROA
118.88.10.0/24NTTCOMNo ROA
118.88.11.0/24NTTCOMNo ROA
118.88.12.0/24NTTCOMNo ROA
118.88.13.0/24NTTCOMNo ROA
118.88.14.0/24NTTCOMNo ROA
118.88.15.0/24NTTCOMNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.