bgpreport

Network · data from 2026-11-12

AS393746 MaxHost.io

Registry name: MAXHOST-IO - Amazing Creations and More LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393746, 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.
2602:f95b::/48 No ROA RIR databaseARIN 635 100% 69
2602:f95b:20::/48 No ROA RIR databaseARIN 635 100% 69
23.186.168.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67
130.12.111.0/24 Valid RIR databaseARIN 667 99% 67
2602:f95b:2::/48 Valid RIR databaseALTDB, ARIN 635 100% 69
2602:f95b:3::/48 Valid RIR databaseARIN 635 100% 69
2602:f95b:69::/48 Valid RIR databaseALTDB, ARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS393746: ARIN::AS-MAXHOST. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS393746 isn't in the set, or no route object for AS393746 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS393746 in itNot covered
ARIN::AS-MAXHOST ARIN4 member sets in no database: AS-COIXIA, AS201398:AS-CUST, AS208753:AS-DANGELO, AS214022:AS-VIRTNET 96131 Yes 0

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

  • ROA: none2
  • AS-SET: missing member4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2602:f95b::/48No ROA covers it. Add a ROA for AS393746, maxLength 48.635 of 636
ROA: none2602:f95b:20::/48No ROA covers it. Add a ROA for AS393746, maxLength 48.635 of 636
AS-SET: missing memberARIN::AS-MAXHOSTAS-MAXHOST (ARIN) lists AS-COIXIA; no IRR database read has it.
AS-SET: missing memberARIN::AS-MAXHOSTAS-MAXHOST (ARIN) lists AS201398:AS-CUST; no IRR database read has it.
AS-SET: missing memberARIN::AS-MAXHOSTAS-MAXHOST (ARIN) lists AS208753:AS-DANGELO; no IRR database read has it.
AS-SET: missing memberARIN::AS-MAXHOSTAS-MAXHOST (ARIN) lists AS214022:AS-VIRTNET; no IRR database read has it.

Route objects not announced

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

2602:f95b:f4::/48ARINValid

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.