bgpreport

Network · data from 2026-11-12

AS263023 AS263023 - INST DE TECN EM INF E INF DO EST DE AL

Registry name: AS263023 - INST DE TECN EM INF E INF DO EST DE AL, BR · not in PeeringDB

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

Announced routes

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

186.249.48.0/21 No ROA Nonecovered by 186.249.48.0/20 672 100% 67
186.249.56.0/21 No ROA Nonecovered by 186.249.48.0/20 672 100% 67
186.249.61.0/24 No ROA Other IRR onlyRADB 672 100% 67
186.249.48.0/20 No ROA Other IRR onlyRADB, TC 668 99% 67

AS-SET

AS263023 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.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none186.249.48.0/21No ROA covers it. Add a ROA for AS263023, maxLength 21.672 of 673
Route object: none186.249.48.0/21No route object for it. A route object for 186.249.48.0/20 with origin AS263023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263023 in the RIR database for the space.672 of 673
ROA: none186.249.56.0/21No ROA covers it. Add a ROA for AS263023, maxLength 21.672 of 673
Route object: none186.249.56.0/21No route object for it. A route object for 186.249.48.0/20 with origin AS263023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263023 in the RIR database for the space.672 of 673
ROA: none186.249.61.0/24No ROA covers it. Add a ROA for AS263023, maxLength 24.672 of 673
Route object: RIR186.249.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none186.249.48.0/20No ROA covers it. Add a ROA for AS263023, maxLength 20.668 of 673
Route object: RIR186.249.48.0/20Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

186.249.52.0/22RADBNo ROA
186.249.56.0/22RADBNo ROA
186.249.60.0/22RADBNo ROA
2801:b2::/32RADB, TCNo 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.