bgpreport

Network · data from 2026-11-12

AS263089 Luxtel

Registry name: AS263089 - V de M Vargas, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263089, 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.
186.250.24.0/23 No ROA Nonecovered by 186.250.24.0/22 671 100% 67
168.195.232.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
186.250.24.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:2a60::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS263089: AS-LUXTEL. 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 (AS263089 isn't in the set, or no route object for AS263089 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 objectsAS263089 in itNot covered
AS-LUXTEL In no IRR database read today.

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

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none186.250.24.0/23No ROA covers it. Add a ROA for AS263089, maxLength 23.671 of 673
Route object: none186.250.24.0/23No route object for it. A route object for 186.250.24.0/22 with origin AS263089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263089 in the RIR database for the space.671 of 673
ROA: none168.195.232.0/22No ROA covers it. Add a ROA for AS263089, maxLength 22.671 of 673
Route object: RIR168.195.232.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none186.250.24.0/22No ROA covers it. Add a ROA for AS263089, maxLength 22.671 of 673
Route object: RIR186.250.24.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:2a60::/32No ROA covers it. Add a ROA for AS263089, maxLength 32.636 of 636
Route object: RIR2804:2a60::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS-LUXTELPeeringDB names AS-LUXTEL; no IRR database read has it.

Route objects not announced

Every route object with origin AS263089 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.