bgpreport

Network · data from 2026-11-12

AS133555 Cortex Network Next-generation Research Centre

Registry name: DOORPOST-AS-AP - DOORPOST Limited, CN · PeeringDB

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

Announced routes

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

44.31.216.0/24 No ROA Other IRR onlyRADB 672 100% 67
2406:840:f380::/44 Valid RIR databaseAPNIC, RADB 634 100% 68
2a06:a005:260::/44 Valid RIR databaseRADB, RIPE 634 100% 68
2a06:a005:270::/44 Valid RIR databaseRIPE 634 100% 68
2a06:a005:280::/44 Valid RIR databaseRIPE 634 100% 68
2a06:a005:290::/44 Valid RIR databaseRIPE 634 100% 68
2a06:a005:2a0::/44 Valid RIR databaseRIPE 634 100% 68
2406:840:fefc::/48 Valid RIR databaseAPNIC 633 100% 69

AS-SET

AS133555'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 32 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: none44.31.216.0/24No ROA covers it. Add a ROA for AS133555, maxLength 24.672 of 673
Route object: RIR44.31.216.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2406:840:f380::/45APNICValid
2406:840:f380::/46APNICValid
2406:840:f380::/47APNICValid
2406:840:f380::/48APNICValid
2406:840:f381::/48APNICValid
2406:840:f382::/47APNICValid
2406:840:f382::/48APNICValid
2406:840:f383::/48APNICValid
2406:840:f384::/46APNICValid
2406:840:f384::/47APNICValid
2406:840:f384::/48APNICValid
2406:840:f385::/48APNICValid
2406:840:f386::/47APNICValid
2406:840:f386::/48APNICValid
2406:840:f387::/48APNICValid
2406:840:f388::/45APNICValid
2406:840:f388::/46APNICValid
2406:840:f388::/47APNICValid
2406:840:f388::/48APNICValid
2406:840:f389::/48APNICValid
2406:840:f38a::/47APNICValid
2406:840:f38a::/48APNICValid
2406:840:f38b::/48APNICValid
2406:840:f38c::/46APNICValid
2406:840:f38c::/47APNICValid
2406:840:f38c::/48APNICValid
2406:840:f38d::/48APNICValid
2406:840:f38e::/47APNICValid
2406:840:f38e::/48APNICValid
2406:840:f38f::/48APNICValid

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.