bgpreport

Network · data from 2026-11-12

AS262550 LUCAS NETWORK INFORMATICA

Registry name: AS262550 - LUCAS NETWORK INFORMATICA LTDA ME, BR · PeeringDB

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

Announced routes

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

38.43.70.0/23 Valid None 668 99% 67
168.197.4.0/23 Valid Other IRR onlyALTDB 672 100% 66
168.197.4.0/24 Valid Other IRR onlyALTDB 672 100% 66
143.0.40.0/22 Valid Other IRR onlyALTDB, RADB 669 99% 66
177.72.168.0/22 Valid Other IRR onlyALTDB 669 99% 66
177.72.172.0/22 Valid Other IRR onlyALTDB 669 99% 66
143.0.40.0/23 Valid Other IRR onlyALTDB 668 99% 66
143.0.42.0/23 Valid Other IRR onlyALTDB 668 99% 66
143.0.43.0/24 Valid Other IRR onlyALTDB 668 99% 66
168.197.7.0/24 Valid Other IRR onlyALTDB 668 99% 67
177.72.168.0/23 Valid Other IRR onlyALTDB 668 99% 66
177.72.170.0/23 Valid Other IRR onlyALTDB 668 99% 66
177.72.170.0/24 Valid Other IRR onlyALTDB 668 99% 66
177.72.171.0/24 Valid Other IRR onlyALTDB 668 99% 66
177.72.172.0/23 Valid Other IRR onlyALTDB 668 99% 66
177.72.174.0/23 Valid Other IRR onlyALTDB 668 99% 66
177.72.175.0/24 Valid Other IRR onlyALTDB 668 99% 66
143.0.42.0/24 Valid Other IRR onlyALTDB 667 99% 66
177.72.174.0/24 Valid Other IRR onlyALTDB 667 99% 66
177.72.168.0/24 Valid Other IRR onlyALTDB 665 99% 67
177.72.169.0/24 Valid Other IRR onlyALTDB 665 99% 67
177.72.172.0/24 Valid Other IRR onlyALTDB 665 99% 67
177.72.173.0/24 Valid Other IRR onlyALTDB 665 99% 67
143.0.40.0/24 Valid Other IRR onlyALTDB 664 99% 67
143.0.41.0/24 Valid Other IRR onlyALTDB 664 99% 67
168.197.6.0/24 Valid Other IRR onlyALTDB 664 99% 67
2804:28e0::/33 Valid Other IRR onlyALTDB 631 99% 69
2804:28e0:8000::/33 Valid Other IRR onlyALTDB 631 99% 69
2804:28e0::/32 Valid Other IRR onlyALTDB, RADB 628 99% 69
168.197.4.0/22 Valid Other IRR onlyALTDB 2 0%low visibility 2
168.197.5.0/24 Valid Other IRR onlyALTDB 2 0%low visibility 2
168.197.6.0/23 Valid Other IRR onlyALTDB 2 0%low visibility 2
38.43.70.0/24 Valid RIR databaseARIN 1 0%low visibility 2
38.43.71.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS262550: AS262550. 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 (AS262550 isn't in the set, or no route object for AS262550 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 objectsAS262550 in itNot covered
AS262550 A single AS number, not a set: AS262550 (this network), 35 route objects.

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

  • Route object: none1
  • Route object: RIR31
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none38.43.70.0/23No route object for it. Add a route object with origin AS262550 in the RIR database for the space.668 of 673
Route object: RIR168.197.4.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.4.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.40.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.72.168.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.72.172.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR143.0.40.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR143.0.42.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR143.0.43.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.197.7.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.168.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.170.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.170.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.171.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.172.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.174.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.175.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR143.0.42.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.72.174.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.72.168.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.72.169.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.72.172.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.72.173.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR143.0.40.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR143.0.41.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR168.197.6.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:28e0::/33Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:28e0:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:28e0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR168.197.4.0/22Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
Route object: RIR168.197.5.0/24Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
Route object: RIR168.197.6.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

177.72.168.0/21RADBNo ROA
2804:45bc::/32ALTDBNo 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.