bgpreport

Network · data from 2026-11-12

AS49683 MASSIVEGRID MASSIVEGRID LTD

Registry name: MASSIVEGRID MASSIVEGRID LTD, GB · not in PeeringDB

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

Announced routes

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

89.33.68.0/22 Invalid: origin Other origin only 1 0%low visibility 2
31.25.236.0/24 Valid RIR databaseRIPE 673 100% 67
31.25.238.0/24 Valid RIR databaseRIPE 673 100% 67
31.25.239.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.172.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.173.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.174.0/24 Valid RIR databaseRIPE 673 100% 67
172.82.64.0/24 Valid RIR databaseARIN, RADB 673 100% 67
172.82.65.0/24 Valid RIR databaseARIN, RADB 673 100% 67
172.82.66.0/24 Valid RIR databaseARIN 673 100% 67
172.82.67.0/24 Valid RIR databaseARIN 673 100% 67
185.44.64.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.44.65.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.44.66.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.85.240.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.85.241.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.85.243.0/24 Valid RIR databaseRIPE 673 100% 67
185.116.236.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.116.237.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.116.238.0/24 Valid RIR databaseRIPE 673 100% 67
185.116.239.0/24 Valid RIR databaseRIPE 673 100% 67
185.122.164.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.122.165.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.122.166.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.168.193.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.184.68.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.184.71.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.189.56.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.189.58.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.189.59.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
31.25.235.0/24 Valid RIR databaseRIPE 672 100% 67
31.25.237.0/24 Valid RIR databaseRIPE 672 100% 67
171.22.175.0/24 Valid RIR databaseRIPE 672 100% 67
185.44.67.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.85.242.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.122.167.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.168.192.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.168.194.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.168.195.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.184.69.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.184.70.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.189.57.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
2a0a:2f00:1::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS49683 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: origin1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin89.33.68.0/22ROAs covering it name AS25369, not AS49683. If AS49683 should announce it, add a ROA for AS49683.1 of 673
Route object: none89.33.68.0/22Route objects for it name AS25369. Add a route object with origin AS49683 in the RIR database for the space.1 of 673

Route objects not announced

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

31.25.234.0/24RADB, RIPEValid
2a0a:2f00:0:1::/64RIPEInvalid: maxLength
2a0a:2f00:2::/48RIPEValid
2a0a:2f00:3::/48RIPEValid

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.