bgpreport

Network · data from 2026-11-12

AS199473 Barnet

Registry name: BARNET SEWERYN TYBORSKI trading as "Barnet", PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199473, 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.
2a03:c0c0::/32 No ROA None 1 0%low visibility 1
185.15.132.0/22 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS199473'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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a03:c0c0::/32No ROA covers it. Add a ROA for AS199473, maxLength 32.1 of 636
Route object: none2a03:c0c0::/32No route object for it. Add a route object with origin AS199473 in the RIR database for the space.1 of 636

Route objects not announced

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

2a10:f781:10:e33::/64RIPENo ROA

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.