bgpreport

Network · data from 2026-11-12

AS151341 The Next Success

Registry name: THENEXTSUCCESS-AS-AP - The Next Success, MM · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS151341, 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.
38.66.213.0/24 Valid Nonecovered by 38.66.212.0/22 670 100% 67
38.66.215.0/24 Valid Nonecovered by 38.66.212.0/22 669 99% 66
38.66.214.0/24 Valid Nonecovered by 38.66.212.0/22 1 0%low visibility 1
103.204.178.0/24 Valid RIR databaseAPNIC 673 100% 68
103.204.179.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67

AS-SET

AS151341'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 21 are in fix.csv.

  • Route object: none3
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: none38.66.213.0/24No route object for it. A route object for 38.66.212.0/22 with origin AS151341 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151341 in the RIR database for the space.670 of 673
Route object: none38.66.215.0/24No route object for it. A route object for 38.66.212.0/22 with origin AS151341 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151341 in the RIR database for the space.669 of 673
Route object: none38.66.214.0/24No route object for it. A route object for 38.66.212.0/22 with origin AS151341 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151341 in the RIR database for the space.1 of 673

Route objects not announced

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

38.66.212.0/22ARINValid
103.204.178.0/23APNICValid
2401:a0::/36APNICValid
2401:a0:1000::/36APNICValid
2401:a0:2000::/36APNICValid
2401:a0:3000::/36APNICValid
2401:a0:4000::/36APNICValid
2401:a0:5000::/36APNICValid
2401:a0:6000::/36APNICValid
2401:a0:7000::/36APNICValid
2401:a0:8000::/36APNICValid
2401:a0:9000::/36APNICValid
2401:a0:a000::/36APNICValid
2401:a0:b000::/36APNICValid
2401:a0:c000::/36APNICValid
2401:a0:d000::/36APNICValid
2401:a0:e000::/36APNICValid
2401:a0:f000::/36APNICValid

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.