bgpreport

Network · data from 2026-11-12

AS263606 COREIT - DATACENTER, SERV GER E INFRA TI

Registry name: AS263606 - COREIT - DATACENTER, SERV GER E INFRA TI LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263606, 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.
177.136.74.0/24 Valid Other IRR onlyRADB 672 100% 67
177.136.72.0/23 Valid Other IRR onlyRADB 670 100% 67
177.136.75.0/24 Valid Other IRR onlyRADB 668 99% 67
2804:fd4::/32 Valid Other IRR onlyALTDB, RADB, TC 632 99% 67
177.136.72.0/24 Valid Other IRR onlyRADB 123 18% 43
177.136.73.0/24 Valid Other IRR onlyRADB 120 18% 42

AS-SET

AS263606'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 8 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR177.136.74.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.136.72.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.136.75.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:fd4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR177.136.72.0/24Route object only in RADB. Add it in the RIR database for the space.123 of 673
Route object: RIR177.136.73.0/24Route object only in RADB. Add it in the RIR database for the space.120 of 673

Route objects not announced

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

177.136.72.0/22ALTDB, RADB, TCNo ROA
177.136.74.0/23RADBNo 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.