bgpreport

Network · data from 2026-11-12

AS269178 J IVANILDO DE SALES MACIEL

Registry name: AS269178 - J IVANILDO DE SALES MACIEL, BR · PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS269178, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269178, 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.
45.181.81.0/24 No ROA Other IRR onlyTC 672 100% 66
45.181.80.0/24 No ROA Other IRR onlyTC 665 99% 67
45.181.82.0/23 No ROA Other IRR onlyTC 665 99% 66
2804:6094::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:6094::/33 No ROA Other IRR onlyTC 331 52% 65
2804:6094:8000::/33 No ROA Other IRR onlyTC 331 52% 65
45.181.82.0/24 No ROA Other IRR onlyTC 130 19% 45
45.181.83.0/24 No ROA Other IRR onlyTC 130 19% 45

AS-SET

AS269178'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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.181.81.0/24No ROA covers it. Add a ROA for AS269178, maxLength 24.672 of 673
Route object: RIR45.181.81.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none45.181.80.0/24No ROA covers it. Add a ROA for AS269178, maxLength 24.665 of 673
Route object: RIR45.181.80.0/24Route object only in TC. Add it in the RIR database for the space.665 of 673
ROA: none45.181.82.0/23No ROA covers it. Add a ROA for AS269178, maxLength 23.665 of 673
Route object: RIR45.181.82.0/23Route object only in TC. Add it in the RIR database for the space.665 of 673
ROA: none2804:6094::/32No ROA covers it. Add a ROA for AS269178, maxLength 32.634 of 636
Route object: RIR2804:6094::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:6094::/33No ROA covers it. Add a ROA for AS269178, maxLength 33.331 of 636
Route object: RIR2804:6094::/33Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none2804:6094:8000::/33No ROA covers it. Add a ROA for AS269178, maxLength 33.331 of 636
Route object: RIR2804:6094:8000::/33Route object only in TC. Add it in the RIR database for the space.331 of 636
ROA: none45.181.82.0/24No ROA covers it. Add a ROA for AS269178, maxLength 24.130 of 673
Route object: RIR45.181.82.0/24Route object only in TC. Add it in the RIR database for the space.130 of 673
ROA: none45.181.83.0/24No ROA covers it. Add a ROA for AS269178, maxLength 24.130 of 673
Route object: RIR45.181.83.0/24Route object only in TC. Add it in the RIR database for the space.130 of 673

Route objects not announced

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

45.181.80.0/22RADB, TCNo ROA
45.181.80.0/23TCNo 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.