bgpreport

Network · data from 2026-11-12

AS56178 LATCH-AS-AP

Registry name: LATCH-AS-AP - Latch Networks Pty Ltd, AU · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.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
7Route objects not announced registered with origin AS56178, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56178, 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.
2001:df0:2c8::/48 No ROA Other IRR onlyRADB 635 100% 67
163.61.26.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS56178'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 9 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2001:df0:2c8::/48No ROA covers it. Add a ROA for AS56178, maxLength 48.635 of 636
Route object: RIR2001:df0:2c8::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.251.4.0/22RADBNo ROA
157.10.208.0/24RADBNo ROA
180.222.192.0/22RADBNo ROA
192.65.84.0/24RADBNo ROA
203.29.253.0/24RADBNo ROA
203.30.57.0/24RADBNo ROA
203.34.254.0/23RADBNo ROA

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.