bgpreport

Network · data from 2026-11-12

AS26722 MAIN-SEQUENCE-TECHNOLOGIES - Main Sequence Technology, Inc.

Registry name: MAIN-SEQUENCE-TECHNOLOGIES - Main Sequence Technology, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26722, 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.
2620:10d:6000::/48 No ROA Nonecovered by 2620:10d:6000::/44 636 100% 67
2620:10d:6001::/48 No ROA Nonecovered by 2620:10d:6000::/44 636 100% 67
2620:10d:6002::/48 No ROA Nonecovered by 2620:10d:6000::/44 636 100% 67
68.171.3.0/24 No ROA Other IRR onlyRADB 672 100% 67
207.220.83.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2620:10d:6000::/48No ROA covers it. Add a ROA for AS26722, maxLength 48.636 of 636
Route object: none2620:10d:6000::/48No route object for it. A route object for 2620:10d:6000::/44 with origin AS26722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26722 in the RIR database for the space.636 of 636
ROA: none2620:10d:6001::/48No ROA covers it. Add a ROA for AS26722, maxLength 48.636 of 636
Route object: none2620:10d:6001::/48No route object for it. A route object for 2620:10d:6000::/44 with origin AS26722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26722 in the RIR database for the space.636 of 636
ROA: none2620:10d:6002::/48No ROA covers it. Add a ROA for AS26722, maxLength 48.636 of 636
Route object: none2620:10d:6002::/48No route object for it. A route object for 2620:10d:6000::/44 with origin AS26722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26722 in the RIR database for the space.636 of 636
ROA: none68.171.3.0/24No ROA covers it. Add a ROA for AS26722, maxLength 24.672 of 673
Route object: RIR68.171.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none207.220.83.0/24No ROA covers it. Add a ROA for AS26722, maxLength 24.672 of 673
Route object: RIR207.220.83.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

207.54.164.0/24RADBValid
2620:10d:6000::/44RADBNo 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.