bgpreport

Network · data from 2026-11-12

AS212449 erate Erate AS

Registry name: erate Erate AS, NO · not in PeeringDB

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

Announced routes

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

149.7.162.0/24 No ROA Nonecovered by 149.7.162.0/23 673 100% 67
149.7.163.0/24 No ROA Nonecovered by 149.7.162.0/23 673 100% 67
149.7.164.0/22 No ROA None 673 100% 67
149.7.164.0/23 No ROA None 673 100% 67
149.7.162.0/23 No ROA Other IRR onlyRADB 673 100% 67
193.32.134.0/23 No ROA RIR databaseRIPE 673 100% 67
193.32.134.0/24 No ROA RIR databaseRIPE 673 100% 67
193.32.135.0/24 No ROA RIR databaseRIPE 673 100% 67
2a09:480:1::/48 No ROA RIR databaseRIPE 634 100% 69
2a09:480:2::/48 No ROA RIR databaseRIPE 634 100% 69
2a09:480::/29 No ROA RIR databaseRIPE 633 100% 69

AS-SET

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

  • ROA: none11
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none149.7.162.0/24No ROA covers it. Add a ROA for AS212449, maxLength 24.673 of 673
Route object: none149.7.162.0/24No route object for it. A route object for 149.7.162.0/23 with origin AS212449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212449 in the RIR database for the space.673 of 673
ROA: none149.7.163.0/24No ROA covers it. Add a ROA for AS212449, maxLength 24.673 of 673
Route object: none149.7.163.0/24No route object for it. A route object for 149.7.162.0/23 with origin AS212449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212449 in the RIR database for the space.673 of 673
ROA: none149.7.164.0/22No ROA covers it. Add a ROA for AS212449, maxLength 22.673 of 673
Route object: none149.7.164.0/22No route object for it. Add a route object with origin AS212449 in the RIR database for the space.673 of 673
ROA: none149.7.164.0/23No ROA covers it. Add a ROA for AS212449, maxLength 23.673 of 673
Route object: none149.7.164.0/23No route object for it. Add a route object with origin AS212449 in the RIR database for the space.673 of 673
ROA: none149.7.162.0/23No ROA covers it. Add a ROA for AS212449, maxLength 23.673 of 673
Route object: RIR149.7.162.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none193.32.134.0/23No ROA covers it. Add a ROA for AS212449, maxLength 23.673 of 673
ROA: none193.32.134.0/24No ROA covers it. Add a ROA for AS212449, maxLength 24.673 of 673
ROA: none193.32.135.0/24No ROA covers it. Add a ROA for AS212449, maxLength 24.673 of 673
ROA: none2a09:480:1::/48No ROA covers it. Add a ROA for AS212449, maxLength 48.634 of 636
ROA: none2a09:480:2::/48No ROA covers it. Add a ROA for AS212449, maxLength 48.634 of 636
ROA: none2a09:480::/29No ROA covers it. Add a ROA for AS212449, maxLength 29.633 of 636

Route objects not announced

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

193.32.132.0/24RIPENo ROA
2a09:480:0:3::/64RIPENo 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.