bgpreport

Network · data from 2026-11-12

AS208360 PNA-AS Pushkarev Nikolai Aleksandrovich

Registry name: PNA-AS Pushkarev Nikolai Aleksandrovich, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208360, 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.
2a11:7680::/32 No ROA RIR databaseRIPE 635 100% 69
2a11:b786::/32 No ROA RIR databaseRIPE 635 100% 69
2a11:d080::/32 No ROA RIR databaseRIPE 635 100% 69
2a0e:67c5::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS208360 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: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a11:7680::/32No ROA covers it. Add a ROA for AS208360, maxLength 32.635 of 636
ROA: none2a11:b786::/32No ROA covers it. Add a ROA for AS208360, maxLength 32.635 of 636
ROA: none2a11:d080::/32No ROA covers it. Add a ROA for AS208360, maxLength 32.635 of 636

Route objects not announced

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

2a0c:2847::/32RIPEValid

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.