bgpreport

Network · data from 2026-11-12

AS28240 AS28240 - VIP - SERVICOS DE TELECOMUNICACOES LTDA.

Registry name: AS28240 - VIP - SERVICOS DE TELECOMUNICACOES LTDA., BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28240, 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:3594::/40 Valid Nonecovered by 2804:3594::/32 633 100% 67
2804:3594:100::/40 Valid Nonecovered by 2804:3594::/32 633 100% 67
2804:3594:2000::/42 Valid Nonecovered by 2804:3594::/32 633 100% 67
187.0.161.0/24 Valid Other IRR onlyRADB 673 100% 67
170.78.204.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
170.78.204.0/23 Valid Other IRR onlyRADB 672 100% 67
187.0.160.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
187.0.160.0/23 Valid Other IRR onlyRADB 672 100% 67
187.0.160.0/24 Valid Other IRR onlyRADB 672 100% 67
187.0.162.0/23 Valid Other IRR onlyRADB 672 100% 67
2804:3594::/32 Valid Other IRR onlyALTDB, RADB 634 100% 67

AS-SET

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

  • Route object: none3
  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:3594::/40No route object for it. A route object for 2804:3594::/32 with origin AS28240 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28240 in the RIR database for the space.633 of 636
Route object: none2804:3594:100::/40No route object for it. A route object for 2804:3594::/32 with origin AS28240 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28240 in the RIR database for the space.633 of 636
Route object: none2804:3594:2000::/42No route object for it. A route object for 2804:3594::/32 with origin AS28240 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28240 in the RIR database for the space.633 of 636
Route object: RIR187.0.161.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.78.204.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.78.204.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.160.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.160.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.160.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.162.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3594::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

170.78.206.0/23RADBValid

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.