bgpreport

Network · data from 2026-11-12

AS271663 ASN271663

Registry name: AS271663 - VICOM BRASIL INTERNET E TELECOM, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 0.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 AS271663, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271663, 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:7f0c:3e00::/40 Valid Nonecovered by 2804:7f0c::/32 633 100% 67
2804:7f0c:3e40::/44 Valid Nonecovered by 2804:7f0c::/32 633 100% 67
2804:7f0c:3e80::/44 Valid Nonecovered by 2804:7f0c::/32 633 100% 67
177.105.200.0/22 Valid Other IRR onlyTC 671 100% 66
177.105.200.0/24 Valid Other IRR onlyTC 671 100% 66
177.105.201.0/24 Valid Other IRR onlyTC 671 100% 66
177.105.202.0/24 Valid Other IRR onlyTC 671 100% 66
177.105.203.0/24 Valid Other IRR onlyTC 671 100% 67

AS-SET

AS271663's PeeringDB record names no 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 9 are in fix.csv.

  • Route object: none3
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:7f0c:3e00::/40No route object for it. A route object for 2804:7f0c::/32 with origin AS271663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271663 in the RIR database for the space.633 of 636
Route object: none2804:7f0c:3e40::/44No route object for it. A route object for 2804:7f0c::/32 with origin AS271663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271663 in the RIR database for the space.633 of 636
Route object: none2804:7f0c:3e80::/44No route object for it. A route object for 2804:7f0c::/32 with origin AS271663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271663 in the RIR database for the space.633 of 636
Route object: RIR177.105.200.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.105.200.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.105.201.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.105.202.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.105.203.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2804:7f0c::/32TCNo 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.