bgpreport

Network · data from 2026-11-12

AS198883 asd-as Tabunscic Anatoli

Registry name: asd-as Tabunscic Anatoli, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198883, 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.
2a14:a087:3::/48 Valid Other origin only 633 100% 67
185.126.67.0/24 Valid RIR databaseRIPE 673 100% 67
193.223.106.0/24 Valid RIR databaseRIPE 673 100% 67
193.223.107.0/24 Valid RIR databaseRIPE 673 100% 67
45.145.56.0/24 Valid RIR databaseRIPE 672 100% 67
195.66.24.0/24 Valid RIR databaseRIPE 672 100% 67
45.149.147.0/24 Valid RIR databaseRIPE 670 100% 67
2a14:a087:4::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a14:a087:3::/48Route objects for it name AS213887. Add a route object with origin AS198883 in the RIR database for the space.633 of 636

Route objects not announced

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

89.33.194.0/24RADBValid

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.