bgpreport

Network · data from 2026-11-12

AS27284 Fourplex Telecom

Registry name: FOURPLEX-ASN - Fourplex Telecom LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27284, 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.
38.225.240.0/24 No ROA Other IRR onlyRADB 4 1%low visibility 3
23.134.76.0/24 Valid RIR databaseARIN 673 100% 67
147.90.234.0/23 Valid RIR databaseRIPE 673 100% 67
158.173.216.0/23 Valid RIR databaseRIPE 673 100% 67
2602:f6f6::/48 Valid RIR databaseARIN 636 100% 67
2602:f6f6:1::/48 Valid RIR databaseARIN 636 100% 67
2602:f6f6:2::/48 Valid RIR databaseARIN 636 100% 67
2602:f6f6:10::/44 Valid RIR databaseARIN 636 100% 67

AS-SET

AS27284's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.225.240.0/24No ROA covers it. Add a ROA for AS27284, maxLength 24.4 of 673
Route object: RIR38.225.240.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673

Route objects not announced

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