bgpreport

Network · data from 2026-11-12

AS201210 TRIGONON-AS TRIGONON DATA SERVICES LTD

Registry name: TRIGONON-AS TRIGONON DATA SERVICES LTD, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201210, 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.

185.82.36.254/32 Valid Nonecovered by 185.82.36.0/24 1 0%low visibility 2
2001:4d70:100::1/128 Valid Nonecovered by 2001:4d70::/32 1 0%low visibility 2
185.82.36.0/24 Valid RIR databaseRIPE 673 100% 67
185.82.38.0/24 Valid RIR databaseRIPE 673 100% 67
185.82.39.0/24 Valid RIR databaseRIPE 673 100% 67
2001:4d70::/32 Valid RIR databaseRIPE 636 100% 67
2a05:8cc0::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS201210 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: none2
ChangePrefix or setDetailFull-table peers
Route object: none185.82.36.254/32No route object for it. A route object for 185.82.36.0/24 with origin AS201210 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS201210 in the RIR database for the space.1 of 673
Route object: none2001:4d70:100::1/128No route object for it. A route object for 2001:4d70::/32 with origin AS201210 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS201210 in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS201210 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.