bgpreport

Network · data from 2026-11-12

AS210673 yangotech Yango Technology Services d.o.o. Beograd

Registry name: yangotech Yango Technology Services d.o.o. Beograd, RS · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS210673, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210673, 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.
2a0d:2a80::/32 No ROA Nonecovered by 2a0d:2a80::/29 634 100% 67
132.243.80.0/20 No ROA RIR databaseRIPE 673 100% 67
2a0d:2a80::/29 No ROA RIR databaseRIPE 633 100% 67

AS-SET

AS210673 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 4 are in fix.csv.

  • ROA: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:2a80::/32No ROA covers it. Add a ROA for AS210673, maxLength 32.634 of 636
Route object: none2a0d:2a80::/32No route object for it. A route object for 2a0d:2a80::/29 with origin AS210673 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210673 in the RIR database for the space.634 of 636
ROA: none132.243.80.0/20No ROA covers it. Add a ROA for AS210673, maxLength 20.673 of 673
ROA: none2a0d:2a80::/29No ROA covers it. Add a ROA for AS210673, maxLength 29.633 of 636

Route objects not announced

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