bgpreport

Network · data from 2026-11-12

AS141217 A.B.S. Online Service

Registry name: ABS1-AS-AP - A.B.S. Online Service, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141217, 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.
138.252.102.0/23 No ROA None 46 7%low visibility 30
122.50.11.0/24 Valid RIR databaseAPNIC 672 100% 67
138.252.102.0/24 Valid RIR databaseAPNIC 672 100% 67
138.252.103.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS141217's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none138.252.102.0/23No ROA covers it. Add a ROA for AS141217, maxLength 23.46 of 673
Route object: none138.252.102.0/23No route object for it. Add a route object with origin AS141217 in the RIR database for the space.46 of 673

Route objects not announced

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

2001:df4:f180::/48APNICValid
2402:34a0::/32APNICValid

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.