bgpreport

Network · data from 2026-11-12

AS22509 BANFIELD - Banfield

Registry name: BANFIELD - Banfield, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22509, 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.
66.193.107.0/24 No ROA None 138 21% 37
209.66.89.0/24 Valid None 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none66.193.107.0/24No ROA covers it. Add a ROA for AS22509, maxLength 24.138 of 673
Route object: none66.193.107.0/24No route object for it. Add a route object with origin AS22509 in the RIR database for the space.138 of 673
Route object: none209.66.89.0/24No route object for it. Add a route object with origin AS22509 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS22509 is announced.

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.