bgpreport

Network · data from 2026-11-12

AS219529 Yulia Kurganova

Registry name: PODRIL1AK2-AS Yulia Kurganova, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219529, 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:7580:6b4::/48 Invalid: origin Nonecovered by 2a14:7580:600::/40 1 0%low visibility 1
2a0d:d940:6a::/48 Valid Other origin onlycovered by 2a0d:d940:60::/44 1 0%low visibility 1
2a0d:d940:6b::/48 Valid Other origin onlycovered by 2a0d:d940:60::/44 1 0%low visibility 1
2a0d:d940:6c::/48 Valid Other origin onlycovered by 2a0d:d940:60::/44 1 0%low visibility 1
2a0d:d940:6d::/48 Valid Other origin onlycovered by 2a0d:d940:60::/44 1 0%low visibility 1
94.249.134.0/24 Valid RIR databaseRIPE 669 99% 66
2a0d:d940:9014::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS219529: AS219529:AS-PODRIL1AK2. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS219529 isn't in the set, or no route object for AS219529 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS219529 in itNot covered
AS219529:AS-PODRIL1AK2 RIPE 010 No 7

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

  • ROA: origin1
  • Route object: none5
  • AS-SET: own ASN1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin2a14:7580:6b4::/48ROAs covering it name AS218569, not AS219529. If AS219529 should announce it, add a ROA for AS219529.1 of 636
Route object: none2a14:7580:6b4::/48No route object for it. A route object for 2a14:7580:600::/40 with origin AS219529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219529 in the RIR database for the space.1 of 636
Route object: none2a0d:d940:6a::/48Route objects for it name AS218569. A route object for 2a0d:d940:60::/44 with origin AS219529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219529 in the RIR database for the space.1 of 636
Route object: none2a0d:d940:6b::/48Route objects for it name AS218569. A route object for 2a0d:d940:60::/44 with origin AS219529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219529 in the RIR database for the space.1 of 636
Route object: none2a0d:d940:6c::/48Route objects for it name AS218569. A route object for 2a0d:d940:60::/44 with origin AS219529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219529 in the RIR database for the space.1 of 636
Route object: none2a0d:d940:6d::/48Route objects for it name AS218569. A route object for 2a0d:d940:60::/44 with origin AS219529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219529 in the RIR database for the space.1 of 636
AS-SET: own ASNAS219529:AS-PODRIL1AK2AS219529 isn't in AS219529:AS-PODRIL1AK2 (RIPE) once expanded. Add AS219529 to it.

Route objects not announced

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

2a0d:d940:60::/44RIPEValid
2a0d:d940:61::/48RADBValid
2a0d:d940:2003::/48RIPEValid
2a0d:d940:2013::/48RIPEValid
2a14:7580:600::/40RIPEInvalid: origin

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.