bgpreport

Network · data from 2026-11-12

AS269786 AS269786 - AIREDATA SRL

Registry name: AS269786 - AIREDATA SRL, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269786, 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.
45.188.208.0/24 Valid Nonecovered by 45.188.208.0/23 672 100% 66
45.188.209.0/24 Valid Nonecovered by 45.188.208.0/23 672 100% 66
45.188.210.0/24 Valid RIR databaseLACNIC 672 100% 66
45.188.211.0/24 Valid RIR databaseLACNIC 672 100% 66

AS-SET

AS269786 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.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none45.188.208.0/24No route object for it. A route object for 45.188.208.0/23 with origin AS269786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269786 in the RIR database for the space.672 of 673
Route object: none45.188.209.0/24No route object for it. A route object for 45.188.208.0/23 with origin AS269786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269786 in the RIR database for the space.672 of 673

Route objects not announced

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

45.188.208.0/22RADBNo ROA
45.188.208.0/23LACNICValid

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.