bgpreport

Network · data from 2026-11-12

AS6747 LATTELEKOM SIA Tet

Registry name: LATTELEKOM SIA Tet, LV · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6747, 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.
91.200.64.0/22 No ROA Other origin only 671 100% 67
78.28.197.0/24 Valid Other origin only 673 100% 67
195.13.180.0/24 Valid RIR databaseRIPE 673 100% 67
80.232.180.0/24 Valid RIR databaseRIPE 672 100% 67
80.232.181.0/24 Valid RIR databaseRIPE 672 100% 67
81.198.93.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none91.200.64.0/22No ROA covers it. Add a ROA for AS6747, maxLength 22.671 of 673
Route object: none91.200.64.0/22Route objects for it name AS43813. Add a route object with origin AS6747 in the RIR database for the space.671 of 673
Route object: none78.28.197.0/24Route objects for it name AS5518. Add a route object with origin AS6747 in the RIR database for the space.673 of 673

Route objects not announced

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

80.233.136.0/24RIPEValid
84.237.255.0/24RIPEInvalid: origin
2a02:16d8:105:9::/64RIPEValid

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.