bgpreport

Network · data from 2026-11-12

AS219498 Artem Kovalchuk

Registry name: TRIFONOV-AS Artem Kovalchuk, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219498, 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.
130.78.11.0/24 Invalid: origin Other origin only 1 0%low visibility 1
177.1.201.0/24 Invalid: origin Other origin only 0 0%low visibility 1
130.78.186.0/24 Valid RIR databaseRIPE 673 100% 67
31.57.66.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
79.182.132.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
104.234.156.0/24 Valid RIR databaseARIN, RADB 672 100% 66
201.3.229.0/24 Valid RIR databaseRIPE 671 100% 68
79.98.36.0/24 Valid RIR databaseRIPE 670 100% 67
45.158.11.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
2a0d:d940:9009::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS219498's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin130.78.11.0/24ROAs covering it name AS215133, not AS219498. If AS219498 should announce it, add a ROA for AS219498.1 of 673
Route object: none130.78.11.0/24Route objects for it name AS215133. Add a route object with origin AS219498 in the RIR database for the space.1 of 673
ROA: origin177.1.201.0/24ROAs covering it name AS218310, not AS219498. If AS219498 should announce it, add a ROA for AS219498.0 of 673
Route object: none177.1.201.0/24Route objects for it name AS218310. Add a route object with origin AS219498 in the RIR database for the space.0 of 673

Route objects not announced

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

77.216.1.0/24RADB, RIPEValid
2a10:ab80:3ed::/48RIPEValid
2a10:ab80:456::/48RIPEValid

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.