bgpreport

Network · data from 2026-11-12

AS30344 365-HOSTING - 365.hosting

Registry name: 365-HOSTING - 365.hosting, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30344, 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.
138.124.187.0/24 No ROA RIR databaseRIPE 1 0%low visibility 1
23.26.1.0/24 Valid RIR databaseARIN 1 0%low visibility 1
23.152.200.0/24 Valid RIR databaseARIN 1 0%low visibility 1
77.91.126.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS30344 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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none138.124.187.0/24No ROA covers it. Add a ROA for AS30344, maxLength 24.1 of 673

Route objects not announced

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

208.69.184.0/21RADBNo ROA
208.69.190.0/23RADBNo ROA
2602:2d3::/40ARINNo 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.