bgpreport

Network · data from 2026-11-12

AS31420 TERASYST-AS Terasyst Ltd

Registry name: TERASYST-AS Terasyst Ltd, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31420, 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.
79.134.171.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.176.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.177.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.178.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.179.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.180.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.181.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.182.0/24 No ROA RIR databaseRIPE 673 100% 66
5.104.184.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.185.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.186.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.187.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.188.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.189.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.190.0/24 Valid RIR databaseRIPE 673 100% 66
5.104.191.0/24 Valid RIR databaseRIPE 673 100% 66
193.151.80.0/24 Valid RIR databaseRIPE 673 100% 66
193.151.81.0/24 Valid RIR databaseRIPE 673 100% 66
193.151.82.0/24 Valid RIR databaseRIPE 673 100% 66
193.151.83.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none79.134.171.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.176.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.177.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.178.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.179.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.180.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.181.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673
ROA: none79.134.182.0/24No ROA covers it. Add a ROA for AS31420, maxLength 24.673 of 673

Route objects not announced

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

5.104.184.0/21RIPEValid
94.156.50.0/24RIPEInvalid: origin
94.156.51.0/24RIPEInvalid: origin
193.151.80.0/22RIPEValid
193.151.80.0/23RIPEInvalid: maxLength
193.151.82.0/23RIPEInvalid: maxLength

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.