bgpreport

Network · data from 2026-11-12

AS41898 DTG-AS SIA "Datu Tehnologiju Grupa"

Registry name: DTG-AS SIA "Datu Tehnologiju Grupa", LV · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41898, 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.
158.255.59.0/24 Valid Other origin onlycovered by 158.255.56.0/21 673 100% 66
91.135.16.0/20 Valid RIR databaseRIPE 673 100% 66
95.130.32.0/21 Valid RIR databaseRIPE 673 100% 66
158.255.56.0/21 Valid RIR databaseRIPE 673 100% 66
2a01:bae0::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none158.255.59.0/24Route objects for it name AS203655. A route object for 158.255.56.0/21 with origin AS41898 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41898 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS41898 is announced.

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.