bgpreport

Network · data from 2026-11-12

AS262549 CELINET INFORMATICA LTDA-ME

Registry name: AS262549 - CELINET INFORMATICA LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262549, 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.72.176.0/21 No ROA Other IRR onlyRADB, TC 672 100% 67
177.72.180.0/23 No ROA Other IRR onlyRADB 672 100% 67
177.72.178.0/23 No ROA Other IRR onlyRADB 670 100% 67
2804:5e8::/32 No ROA Other IRR onlyRADB, TC 636 100% 69

AS-SET

AS262549'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 20 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none177.72.176.0/21No ROA covers it. Add a ROA for AS262549, maxLength 21.672 of 673
Route object: RIR177.72.176.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.72.180.0/23No ROA covers it. Add a ROA for AS262549, maxLength 23.672 of 673
Route object: RIR177.72.180.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.72.178.0/23No ROA covers it. Add a ROA for AS262549, maxLength 23.670 of 673
Route object: RIR177.72.178.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:5e8::/32No ROA covers it. Add a ROA for AS262549, maxLength 32.636 of 636
Route object: RIR2804:5e8::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.72.176.0/22RADBNo ROA
177.72.176.0/23RADBNo ROA
177.72.176.0/24RADBNo ROA
177.72.177.0/24RADBNo ROA
177.72.178.0/24RADBNo ROA
177.72.179.0/24RADBNo ROA
177.72.180.0/22RADBNo ROA
177.72.180.0/24RADBNo ROA
177.72.181.0/24RADBNo ROA
177.72.182.0/23RADBNo ROA
177.72.182.0/24RADBNo ROA
177.72.183.0/24RADBNo 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.