bgpreport

Network · data from 2026-11-12

AS262378 Compuservice Empreendimentos

Registry name: AS262378 - Compuservice Empreendimentos Ltda, BR · PeeringDB

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

Announced routes

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

2804:2d80::/48 Valid Nonecovered by 2804:2d80::/33 631 99% 68
177.131.21.0/24 Valid Other IRR onlyRADB 672 100% 66
177.131.31.0/24 Valid Other IRR onlyRADB 672 100% 66
177.131.29.0/24 Valid Other IRR onlyRADB 671 100% 67
177.131.30.0/24 Valid Other IRR onlyRADB 671 100% 67
170.79.195.0/24 Valid Other IRR onlyRADB 669 99% 66
170.79.193.0/24 Valid Other IRR onlyRADB 668 99% 67
177.131.18.0/23 Valid Other IRR onlyRADB 668 99% 67
177.131.24.0/23 Valid Other IRR onlyRADB 668 99% 67
177.131.28.0/23 Valid Other IRR onlyRADB 668 99% 66
170.79.192.0/24 Valid Other IRR onlyRADB 666 99% 67
170.79.194.0/24 Valid Other IRR onlyRADB 666 99% 66
177.131.16.0/20 Valid Other IRR onlyALTDB, RADB 664 99% 66
177.131.22.0/23 Valid Other IRR onlyRADB 664 99% 67
2804:2d80::/32 Valid Other IRR onlyALTDB, RADB 631 99% 67
2804:2d80:2::/48 Valid Other IRR onlyRADB 631 99% 67
2804:2d80:3::/48 Valid Other IRR onlyRADB 631 99% 67
2804:2d80:face::/48 Valid Other IRR onlyRADB 631 99% 67
2804:2d80:5::/48 Valid Other IRR onlyRADB 630 99% 67
2804:2d80:700::/40 Valid Other IRR onlyRADB 630 99% 67
2804:2d80:aa00::/40 Valid Other IRR onlyRADB 630 99% 67
2804:2d80:aa00::/48 Valid Other IRR onlyRADB 630 99% 67
2804:2d80:ae00::/39 Valid Other IRR onlyRADB 630 99% 67
2804:2d80:40::/42 Valid Other IRR onlyRADB 628 99% 67
2804:2d80:ab00::/40 Valid Other IRR onlyRADB 628 99% 67
177.131.16.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS262378: AS262378:AS-CUSTOMERS. 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 (AS262378 isn't in the set, or no route object for AS262378 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 objectsAS262378 in itNot covered
AS262378:AS-CUSTOMERS ALTDB 111120 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 41 are in fix.csv.

  • Route object: none1
  • Route object: RIR25
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2804:2d80::/48No route object for it. A route object for 2804:2d80::/33 with origin AS262378 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262378 in the RIR database for the space.631 of 636
Route object: RIR177.131.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.131.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.131.29.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.131.30.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.79.195.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.79.193.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.131.18.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.131.24.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.131.28.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.79.192.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR170.79.194.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.131.16.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR177.131.22.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:2d80::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2d80:2::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2d80:3::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2d80:face::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2d80:5::/48Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d80:700::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d80:aa00::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d80:aa00::/48Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d80:ae00::/39Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d80:40::/42Route object only in RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:2d80:ab00::/40Route object only in RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR177.131.16.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

170.79.192.0/22ALTDB, RADBValid
177.131.16.0/22RADBValid
177.131.18.0/24RADBValid
177.131.22.0/24RADBValid
177.131.24.0/22RADBValid
177.131.24.0/24RADBValid
177.131.26.0/24RADBValid
177.131.27.0/24RADBValid
177.131.28.0/24RADBValid
177.131.30.0/23RADBValid
2804:2d80::/33RADBValid
2804:2d80:500::/41RADBValid
2804:2d80:560::/43RADBValid
2804:2d80:8000::/33RADBValid
2804:2d80:aa02::/48RADBValid

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.