bgpreport

Network · data from 2026-11-12

AS46370 GRANDWEB - Grand Web Solutions, Inc.

Registry name: GRANDWEB - Grand Web Solutions, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46370, 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.
84.75.204.0/24 Invalid: origin Other origin only 2 0%low visibility 2
95.135.199.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.92.145.0/24 Invalid: origin None 2 0%low visibility 2
87.232.99.0/24 No ROA None 1 0%low visibility 1
213.130.159.0/24 Valid Other IRR onlyRADB 669 99% 67
213.218.209.0/24 Valid Other IRR onlyRADB 669 99% 67
50.118.229.0/24 Valid RIR databaseARIN, RADB 669 99% 67
64.81.179.0/24 Valid RIR databaseARIN, RADB 669 99% 67
103.21.139.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
220.158.205.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67

AS-SET

AS46370 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 10 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: origin84.75.204.0/24ROAs covering it name AS834, not AS46370. If AS46370 should announce it, add a ROA for AS46370.2 of 673
Route object: none84.75.204.0/24Route objects for it name AS834. Add a route object with origin AS46370 in the RIR database for the space.2 of 673
ROA: origin95.135.199.0/24ROAs covering it name AS152606, not AS46370. If AS46370 should announce it, add a ROA for AS46370.2 of 673
Route object: none95.135.199.0/24Route objects for it name AS152606. Add a route object with origin AS46370 in the RIR database for the space.2 of 673
ROA: origin178.92.145.0/24ROAs covering it name AS834, not AS46370. If AS46370 should announce it, add a ROA for AS46370.2 of 673
Route object: none178.92.145.0/24No route object for it. Add a route object with origin AS46370 in the RIR database for the space.2 of 673
ROA: none87.232.99.0/24No ROA covers it. Add a ROA for AS46370, maxLength 24.1 of 673
Route object: none87.232.99.0/24No route object for it. Add a route object with origin AS46370 in the RIR database for the space.1 of 673
Route object: RIR213.130.159.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR213.218.209.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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