bgpreport

Network · data from 2026-11-12

AS262699 Fox Internet

Registry name: AS262699 - FOX Internet Banda Larga, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262699, 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.

187.102.64.0/20 No ROA Other IRR onlyRADB, TC 671 100% 67
177.125.224.0/21 No ROA Other IRR onlyRADB, TC 670 100% 67
187.102.66.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:48c::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
187.102.64.0/21 No ROA Other IRR onlyRADB 2 0%low visibility 2
187.102.72.0/21 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS262699: AS-FOXINTERNET. 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 (AS262699 isn't in the set, or no route object for AS262699 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 objectsAS262699 in itNot covered
AS-FOXINTERNET TClists itself further down4 member sets in no database: AS262282:AS-ALL, AS263320:AS-ALL, AS52548:AS-ALL, AS61775:AS-ALL 135202,990 Yes 0

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

  • ROA: none6
  • Route object: RIR6
  • AS-SET: missing member4
  • Route object: not announced71
ChangePrefix or setDetailFull-table peers
ROA: none187.102.64.0/20No ROA covers it. Add a ROA for AS262699, maxLength 20.671 of 673
Route object: RIR187.102.64.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.125.224.0/21No ROA covers it. Add a ROA for AS262699, maxLength 21.670 of 673
Route object: RIR177.125.224.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none187.102.66.0/24No ROA covers it. Add a ROA for AS262699, maxLength 24.670 of 673
Route object: RIR187.102.66.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:48c::/32No ROA covers it. Add a ROA for AS262699, maxLength 32.633 of 636
Route object: RIR2804:48c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none187.102.64.0/21No ROA covers it. Add a ROA for AS262699, maxLength 21.2 of 673
Route object: RIR187.102.64.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none187.102.72.0/21No ROA covers it. Add a ROA for AS262699, maxLength 21.2 of 673
Route object: RIR187.102.72.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: missing memberAS-FOXINTERNETAS-FOXINTERNET (TC) lists AS262282:AS-ALL; no IRR database read has it.
AS-SET: missing memberAS-FOXINTERNETAS-FOXINTERNET (TC) lists AS263320:AS-ALL; no IRR database read has it.
AS-SET: missing memberAS-FOXINTERNETAS-FOXINTERNET (TC) lists AS52548:AS-ALL; no IRR database read has it.
AS-SET: missing memberAS-FOXINTERNETAS-FOXINTERNET (TC) lists AS61775:AS-ALL; no IRR database read has it.

Route objects not announced

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

177.125.224.0/22RADBNo ROA
177.125.224.0/23RADBNo ROA
177.125.224.0/24RADBNo ROA
177.125.225.0/24RADBNo ROA
177.125.226.0/23RADBNo ROA
177.125.226.0/24RADBNo ROA
177.125.227.0/24RADBNo ROA
177.125.228.0/22RADBNo ROA
177.125.228.0/23RADBNo ROA
177.125.228.0/24RADBNo ROA
177.125.229.0/24RADBNo ROA
177.125.230.0/23RADBNo ROA
177.125.230.0/24RADBNo ROA
177.125.231.0/24RADBNo ROA
187.102.64.0/22RADBNo ROA
187.102.64.0/23RADBNo ROA
187.102.64.0/24RADBNo ROA
187.102.65.0/24RADBNo ROA
187.102.66.0/23RADBNo ROA
187.102.67.0/24RADBNo ROA
187.102.68.0/22RADBNo ROA
187.102.68.0/23RADBNo ROA
187.102.68.0/24RADBNo ROA
187.102.69.0/24RADBNo ROA
187.102.70.0/23RADBNo ROA
187.102.70.0/24RADBNo ROA
187.102.71.0/24RADBNo ROA
187.102.72.0/22RADBNo ROA
187.102.72.0/23RADBNo ROA
187.102.72.0/24RADBNo ROA
187.102.73.0/24RADBNo ROA
187.102.74.0/23RADBNo ROA
187.102.74.0/24RADBNo ROA
187.102.75.0/24RADBNo ROA
187.102.76.0/22RADBNo ROA
187.102.76.0/23RADBNo ROA
187.102.76.0/24RADBNo ROA
187.102.77.0/24RADBNo ROA
187.102.78.0/23RADBNo ROA
187.102.78.0/24RADBNo ROA
187.102.79.0/24RADBNo ROA
2804:48c::/33RADBNo ROA
2804:48c::/34RADBNo ROA
2804:48c::/35RADBNo ROA
2804:48c::/36RADBNo ROA
2804:48c:1000::/36RADBNo ROA
2804:48c:2000::/35RADBNo ROA
2804:48c:2000::/36RADBNo ROA
2804:48c:3000::/36RADBNo ROA
2804:48c:4000::/34RADBNo ROA
2804:48c:4000::/35RADBNo ROA
2804:48c:4000::/36RADBNo ROA
2804:48c:5000::/36RADBNo ROA
2804:48c:6000::/35RADBNo ROA
2804:48c:6000::/36RADBNo ROA
2804:48c:7000::/36RADBNo ROA
2804:48c:8000::/33RADBNo ROA
2804:48c:8000::/34RADBNo ROA
2804:48c:8000::/35RADBNo ROA
2804:48c:8000::/36RADBNo ROA
2804:48c:9000::/36RADBNo ROA
2804:48c:a000::/35RADBNo ROA
2804:48c:a000::/36RADBNo ROA
2804:48c:b000::/36RADBNo ROA
2804:48c:c000::/34RADBNo ROA
2804:48c:c000::/35RADBNo ROA
2804:48c:c000::/36RADBNo ROA
2804:48c:d000::/36RADBNo ROA
2804:48c:e000::/35RADBNo ROA
2804:48c:e000::/36RADBNo ROA
2804:48c:f000::/36RADBNo 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.