bgpreport

Network · data from 2026-11-12

AS33059 Momentum Telecom AS33059

Registry name: MOMENTUM33059 - Momentum Telecom, Inc., US · PeeringDB

21IPv4 routes 76.2% RPKI valid · 66.7% with a route object
9IPv6 routes 77.8% RPKI valid · 77.8% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 9 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS33059, seen from no peer

Announced routes

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

64.92.66.0/23 No ROA Nonecovered by 64.92.64.0/20 673 100% 67
2605:8300:ff01::/48 No ROA Nonecovered by 2605:8300::/32 635 100% 67
64.92.68.0/24 No ROA Nonecovered by 64.92.64.0/20 111 16% 38
137.239.209.0/24 No ROA Other IRR onlyRADB 673 100% 67
209.35.104.0/24 No ROA Other IRR onlyRADB 673 100% 67
74.117.190.0/24 No ROA Other IRR onlyRADB 71 11% 39
2606:840::/32 No ROA Other IRR onlyRADB 61 10%low visibility 35
64.92.70.0/24 Valid Nonecovered by 64.92.64.0/20 673 100% 67
64.92.81.0/24 Valid None 673 100% 67
209.35.109.0/24 Valid None 673 100% 67
64.92.74.0/24 Valid Nonecovered by 64.92.64.0/20 672 100% 67
2605:8300:18::/48 Valid Nonecovered by 2605:8300::/32 635 100% 67
64.92.77.0/24 Valid Nonecovered by 64.92.64.0/20 2 0%low visibility 2
64.92.73.0/24 Valid Other IRR onlyRADB 673 100% 67
64.92.86.0/24 Valid Other IRR onlyRADB 673 100% 67
209.35.107.0/24 Valid Other IRR onlyRADB 673 100% 67
209.35.108.0/24 Valid Other IRR onlyRADB 673 100% 67
199.175.7.0/24 Valid Other IRR onlyRADB 672 100% 67
204.174.29.0/24 Valid Other IRR onlyRADB 672 100% 67
204.174.31.0/24 Valid Other IRR onlyRADB 672 100% 67
209.35.106.0/24 Valid Other IRR onlyRADB 672 100% 67
137.239.197.0/24 Valid Other IRR onlyRADB 671 100% 67
2605:8300:10::/48 Valid Other IRR onlyRADB 635 100% 67
2605:8300:19::/48 Valid Other IRR onlyRADB 635 100% 68
2605:8300:12::/48 Valid Other IRR onlyRADB 634 100% 68
2605:8300:5::/48 Valid Other IRR onlyRADB 605 95% 67
2605:8300:9::/48 Valid Other IRR onlyRADB 605 95% 67
2605:8300:a::/48 Valid Other IRR onlyRADB 605 95% 67
137.239.220.0/24 Valid RIR databaseARIN, RADB 672 100% 67
209.42.167.0/24 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS33059: RADB::AS-MTMACCESSSA. 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 (AS33059 isn't in the set, or no route object for AS33059 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 objectsAS33059 in itNot covered
RADB::AS-MTMACCESSSA RADB2 member sets in no database: AS-EDGEWELL, AS-SAMUEL-A-RAMIREZ 101822 Yes 2

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

  • ROA: none7
  • Route object: none9
  • Route object: RIR19
  • AS-SET: missing member2
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none64.92.66.0/23No ROA covers it. Add a ROA for AS33059, maxLength 23.673 of 673
Route object: none64.92.66.0/23No route object for it. A route object for 64.92.64.0/20 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.673 of 673
ROA: none2605:8300:ff01::/48No ROA covers it. Add a ROA for AS33059, maxLength 48.635 of 636
Route object: none2605:8300:ff01::/48No route object for it. A route object for 2605:8300::/32 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.635 of 636
ROA: none64.92.68.0/24No ROA covers it. Add a ROA for AS33059, maxLength 24.111 of 673
Route object: none64.92.68.0/24No route object for it. A route object for 64.92.64.0/20 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.111 of 673
ROA: none137.239.209.0/24No ROA covers it. Add a ROA for AS33059, maxLength 24.673 of 673
Route object: RIR137.239.209.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.35.104.0/24No ROA covers it. Add a ROA for AS33059, maxLength 24.673 of 673
Route object: RIR209.35.104.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.117.190.0/24No ROA covers it. Add a ROA for AS33059, maxLength 24.71 of 673
Route object: RIR74.117.190.0/24Route object only in RADB. Add it in the RIR database for the space.71 of 673
ROA: none2606:840::/32No ROA covers it. Add a ROA for AS33059, maxLength 32.61 of 636
Route object: RIR2606:840::/32Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: none64.92.70.0/24No route object for it. A route object for 64.92.64.0/20 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.673 of 673
Route object: none64.92.81.0/24No route object for it. Add a route object with origin AS33059 in the RIR database for the space.673 of 673
Route object: none209.35.109.0/24No route object for it. Add a route object with origin AS33059 in the RIR database for the space.673 of 673
Route object: none64.92.74.0/24No route object for it. A route object for 64.92.64.0/20 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.672 of 673
Route object: none2605:8300:18::/48No route object for it. A route object for 2605:8300::/32 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.635 of 636
Route object: none64.92.77.0/24No route object for it. A route object for 64.92.64.0/20 with origin AS33059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33059 in the RIR database for the space.2 of 673
Route object: RIR64.92.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR64.92.86.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR209.35.107.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR209.35.108.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR199.175.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.174.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR204.174.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.35.106.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR137.239.197.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2605:8300:10::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2605:8300:19::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2605:8300:12::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2605:8300:5::/48Route object only in RADB. Add it in the RIR database for the space.605 of 636
Route object: RIR2605:8300:9::/48Route object only in RADB. Add it in the RIR database for the space.605 of 636
Route object: RIR2605:8300:a::/48Route object only in RADB. Add it in the RIR database for the space.605 of 636
AS-SET: missing memberRADB::AS-MTMACCESSSAAS-MTMACCESSSA (RADB) lists AS-EDGEWELL; no IRR database read has it.
AS-SET: missing memberRADB::AS-MTMACCESSSAAS-MTMACCESSSA (RADB) lists AS-SAMUEL-A-RAMIREZ; no IRR database read has it.

Route objects not announced

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

64.92.64.0/20RADBNo ROA
64.92.71.0/24RADBValid
64.92.80.0/24RADBValid
64.92.82.0/24RADBValid
64.92.83.0/24RADBValid
64.92.85.0/24RADBValid
64.92.92.0/24RADBValid
137.239.196.0/24RADBValid
137.239.198.0/24RADBValid
137.239.201.0/24RADBValid
137.239.202.0/24RADBValid
137.239.203.0/24RADBValid
137.239.204.0/24RADBValid
137.239.205.0/24RADBValid
137.239.206.0/24RADBValid
204.16.48.0/22RADBNo ROA
204.16.52.0/22RADBNo ROA
204.174.17.0/24RADBValid
204.174.28.0/24RADBValid
204.174.30.0/24RADBValid
209.35.110.0/24RADBNo ROA
209.35.111.0/24RADBNo ROA
2605:8300::/32RADBNo ROA
2605:8300::/47ALTDBNo ROA
2605:8300:1::/48RADBValid
2605:8300:3::/48RADBValid
2605:8300:4::/48RADBValid
2605:8300:6::/48RADBValid
2605:8300:7::/48RADBValid
2605:8300:b::/48RADBValid
2605:8300:11::/48RADBValid
2607:b600::/32RADBNo 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.