bgpreport

Network · data from 2026-11-12

AS214848

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214848, 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.

5.253.39.0/24 Invalid: origin Other origin only 2 0%low visibility 2

AS-SET

AS214848 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 35 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: origin5.253.39.0/24ROAs covering it name AS199550, not AS214848. If AS214848 should announce it, add a ROA for AS214848.2 of 673
Route object: none5.253.39.0/24Route objects for it name AS199550. Add a route object with origin AS214848 in the RIR database for the space.2 of 673

Route objects not announced

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

2406:840:e380::/44APNICValid
2406:840:e380::/45APNICValid
2406:840:e380::/46APNICValid
2406:840:e380::/47APNICValid
2406:840:e380::/48APNICValid
2406:840:e381::/48APNICValid
2406:840:e382::/47APNICValid
2406:840:e382::/48APNICValid
2406:840:e383::/48APNICValid
2406:840:e384::/46APNICValid
2406:840:e384::/47APNICValid
2406:840:e384::/48APNICValid
2406:840:e385::/48APNICValid
2406:840:e386::/47APNICValid
2406:840:e386::/48APNICValid
2406:840:e387::/48APNICValid
2406:840:e388::/45APNICValid
2406:840:e388::/46APNICValid
2406:840:e388::/47APNICValid
2406:840:e388::/48APNICValid
2406:840:e389::/48APNICValid
2406:840:e38a::/47APNICValid
2406:840:e38a::/48APNICValid
2406:840:e38b::/48APNICValid
2406:840:e38c::/46APNICValid
2406:840:e38c::/47APNICValid
2406:840:e38c::/48APNICValid
2406:840:e38d::/48APNICValid
2406:840:e38e::/47APNICValid
2406:840:e38e::/48APNICValid
2406:840:e38f::/48APNICValid
2602:f486:fe::/48ARINValid
2a14:67c2:800::/40RADBValid

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.