bgpreport

Network · data from 2026-11-12

AS327893 Legends Connect Pty Ltd

Registry name: Legends Connect Pty Ltd - Legends Connect Pty Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327893, 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.
102.128.168.0/24 Valid Other IRR onlyRADB 673 100% 66
102.128.169.0/24 Valid Other IRR onlyRADB 673 100% 66
102.128.170.0/24 Valid Other IRR onlyRADB 673 100% 66
102.128.171.0/24 Valid Other IRR onlyRADB 673 100% 66
169.255.220.0/24 Valid Other IRR onlyRADB 673 100% 66
169.255.221.0/24 Valid Other IRR onlyRADB 673 100% 66
169.255.222.0/24 Valid Other IRR onlyRADB 673 100% 66
169.255.223.0/24 Valid Other IRR onlyRADB 673 100% 66
102.128.168.0/22 Valid RIR databaseAFRINIC 2 0%low visibility 2
169.255.220.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS327893: AS-LEGENDS-CONNECT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS327893 isn't in the set, or no route object for AS327893 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS327893 in itNot covered
AS-LEGENDS-CONNECT AFRINIC1 member set in no database: AS-327893 010 No 10

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

  • Route object: RIR8
  • AS-SET: own ASN1
  • AS-SET: missing member1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR102.128.168.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR102.128.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR102.128.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR102.128.171.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR169.255.220.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR169.255.221.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR169.255.222.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR169.255.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: own ASNAS-LEGENDS-CONNECTAS327893 isn't in AS-LEGENDS-CONNECT (AFRINIC) once expanded. Add AS327893 to it.
AS-SET: missing memberAS-LEGENDS-CONNECTAS-LEGENDS-CONNECT (AFRINIC) lists AS-327893; no IRR database read has it.

Route objects not announced

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

2c0f:f480::/32AFRINICNo 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.