bgpreport

Network · data from 2026-11-12

AS271569 EDA INFO

Registry name: AS271569 - EDA INFO, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271569, 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.
179.63.28.0/22 No ROA Other IRR onlyTC 672 100% 66
179.63.28.0/23 No ROA Other IRR onlyTC 672 100% 66
179.63.30.0/23 No ROA Other IRR onlyTC 672 100% 66
179.63.28.0/24 No ROA Other IRR onlyTC 209 31% 56
179.63.29.0/24 No ROA Other IRR onlyTC 209 31% 56
179.63.30.0/24 No ROA Other IRR onlyTC 209 31% 56
179.63.31.0/24 No ROA Other IRR onlyTC 209 31% 56
2804:7d90::/32 No ROA Other IRR onlyRADB, TC 10 2%low visibility 8
2804:7d90:1::/48 No ROA Other IRR onlyTC 9 1%low visibility 7

AS-SET

AS271569'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: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none179.63.28.0/22No ROA covers it. Add a ROA for AS271569, maxLength 22.672 of 673
Route object: RIR179.63.28.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none179.63.28.0/23No ROA covers it. Add a ROA for AS271569, maxLength 23.672 of 673
Route object: RIR179.63.28.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none179.63.30.0/23No ROA covers it. Add a ROA for AS271569, maxLength 23.672 of 673
Route object: RIR179.63.30.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none179.63.28.0/24No ROA covers it. Add a ROA for AS271569, maxLength 24.209 of 673
Route object: RIR179.63.28.0/24Route object only in TC. Add it in the RIR database for the space.209 of 673
ROA: none179.63.29.0/24No ROA covers it. Add a ROA for AS271569, maxLength 24.209 of 673
Route object: RIR179.63.29.0/24Route object only in TC. Add it in the RIR database for the space.209 of 673
ROA: none179.63.30.0/24No ROA covers it. Add a ROA for AS271569, maxLength 24.209 of 673
Route object: RIR179.63.30.0/24Route object only in TC. Add it in the RIR database for the space.209 of 673
ROA: none179.63.31.0/24No ROA covers it. Add a ROA for AS271569, maxLength 24.209 of 673
Route object: RIR179.63.31.0/24Route object only in TC. Add it in the RIR database for the space.209 of 673
ROA: none2804:7d90::/32No ROA covers it. Add a ROA for AS271569, maxLength 32.10 of 636
Route object: RIR2804:7d90::/32Route object only in RADB, TC. Add it in the RIR database for the space.10 of 636
ROA: none2804:7d90:1::/48No ROA covers it. Add a ROA for AS271569, maxLength 48.9 of 636
Route object: RIR2804:7d90:1::/48Route object only in TC. Add it in the RIR database for the space.9 of 636

Route objects not announced

Every route object with origin AS271569 is announced.

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.