bgpreport

Network · data from 2026-11-12

AS55454 TWO-DEGREES-AS-AP - Two Degrees Mobile Limited

Registry name: TWO-DEGREES-AS-AP - Two Degrees Mobile Limited, NZ · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
1IPv6 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
3Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS55454, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55454, 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.
116.199.208.0/20 No ROA Other IRR onlyRADB 672 100% 68
182.23.176.0/21 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
202.50.246.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2404:1c00::/32 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

AS55454 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 16 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none116.199.208.0/20No ROA covers it. Add a ROA for AS55454, maxLength 20.672 of 673
Route object: RIR116.199.208.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

182.23.176.0/22APNICValid
182.23.176.0/23APNICValid
182.23.176.0/24APNICValid
182.23.177.0/24APNICValid
182.23.178.0/23APNICValid
182.23.178.0/24APNICValid
182.23.179.0/24APNICValid
182.23.180.0/22APNICValid
182.23.180.0/23APNICValid
182.23.180.0/24APNICValid
182.23.181.0/24APNICValid
182.23.182.0/23APNICValid
182.23.182.0/24APNICValid
182.23.183.0/24APNICValid

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.