bgpreport

Network · data from 2026-11-12

AS2726 Webformix

Registry name: AS-WEBFORMIX - Webformix, US · PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
4Route objects not announced registered with origin AS2726, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2726, 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.
68.67.96.0/20 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
130.51.208.0/22 No ROA RIR databaseARIN, RADB 671 100% 68

AS-SET

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

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none68.67.96.0/20No ROA covers it. Add a ROA for AS2726, maxLength 20.671 of 673
Route object: RIR68.67.96.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none130.51.208.0/22No ROA covers it. Add a ROA for AS2726, maxLength 22.671 of 673

Route objects not announced

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

68.67.96.0/21NTTCOMNo ROA
68.67.97.0/24RADBNo ROA
68.67.104.0/21NTTCOMNo ROA
2606:da80::/36ARINNo 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.