bgpreport

Network · data from 2026-11-12

AS31786 PloxHost

Registry name: ZOOMINGWORK-LLC - PloxHost, US · PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object
3IPv6 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
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS31786, seen from no peer

Announced routes

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

46.202.225.0/24 Invalid: origin Other origin only 3 0%low visibility 3
2602:fba3:f00::/48 Valid RIR databaseARIN 635 100% 69
2606:fc40:4001::/48 Valid RIR databaseARIN 635 100% 69
172.111.48.0/24 Valid RIR databaseARIN 463 69% 66
199.253.30.0/24 Valid RIR databaseARIN 462 69% 66
2602:ffc5:500::/40 Valid RIR databaseARIN 21 3%low visibility 20

AS-SET

PeeringDB's irr_as_set for AS31786: AS-ZOOMINGWORK-LLC. 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 (AS31786 isn't in the set, or no route object for AS31786 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 objectsAS31786 in itNot covered
AS-ZOOMINGWORK-LLC ARIN 6146 Yes 1

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin46.202.225.0/24ROAs covering it name AS834, AS20473, not AS31786. If AS31786 should announce it, add a ROA for AS31786.3 of 673
Route object: none46.202.225.0/24Route objects for it name AS834, AS20473. Add a route object with origin AS31786 in the RIR database for the space.3 of 673

Route objects not announced

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

38.117.190.0/24RADBNo ROA
66.85.44.0/24ARINValid
2602:fb54:146::/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.