bgpreport

Network · data from 2026-11-12

AS200946 RSA-AS EMC Information Systems International PUC

Registry name: RSA-AS EMC Information Systems International PUC, IE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200946, 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.
198.161.246.0/24 No ROA Other origin only 673 100% 67
204.180.228.0/24 No ROA None 673 100% 67
208.23.212.0/24 No ROA Other origin only 673 100% 67
84.207.232.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
84.207.246.0/24 Valid RIR databaseRADB, RIPE 673 100% 67

AS-SET

AS200946 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 6 are in fix.csv.

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none198.161.246.0/24No ROA covers it. Add a ROA for AS200946, maxLength 24.673 of 673
Route object: none198.161.246.0/24Route objects for it name AS198949. Add a route object with origin AS200946 in the RIR database for the space.673 of 673
ROA: none204.180.228.0/24No ROA covers it. Add a ROA for AS200946, maxLength 24.673 of 673
Route object: none204.180.228.0/24No route object for it. Add a route object with origin AS200946 in the RIR database for the space.673 of 673
ROA: none208.23.212.0/24No ROA covers it. Add a ROA for AS200946, maxLength 24.673 of 673
Route object: none208.23.212.0/24Route objects for it name AS198949. Add a route object with origin AS200946 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS200946 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.