bgpreport

Network · data from 2026-11-12

AS40193 AS-TRIT - Trit Networks, LLC

Registry name: AS-TRIT - Trit Networks, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40193, 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.
208.90.38.0/24 No ROA Nonecovered by 208.90.32.0/21 664 99% 68
104.244.63.0/24 No ROA Other IRR onlyALTDB 664 99% 68
208.90.32.0/24 No ROA Other IRR onlyALTDB 664 99% 68
104.193.228.0/22 No ROA Other IRR onlyALTDB 663 99% 68
104.244.56.0/21 No ROA Other IRR onlyALTDB 663 99% 68
208.75.88.0/22 No ROA Other IRR onlyALTDB 663 99% 68
208.90.32.0/21 No ROA Other IRR onlyALTDB 663 99% 68
209.159.128.0/20 No ROA Other IRR onlyALTDB 663 99% 68
2610:1a0::/32 No ROA Other IRR onlyALTDB 631 99% 70
2610:1a0:70::/44 No ROA Other IRR onlyALTDB 631 99% 70
2610:1a0:a0::/44 No ROA Other IRR onlyALTDB 631 99% 70

AS-SET

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

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none208.90.38.0/24No ROA covers it. Add a ROA for AS40193, maxLength 24.664 of 673
Route object: none208.90.38.0/24No route object for it. A route object for 208.90.32.0/21 with origin AS40193 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40193 in the RIR database for the space.664 of 673
ROA: none104.244.63.0/24No ROA covers it. Add a ROA for AS40193, maxLength 24.664 of 673
Route object: RIR104.244.63.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
ROA: none208.90.32.0/24No ROA covers it. Add a ROA for AS40193, maxLength 24.664 of 673
Route object: RIR208.90.32.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
ROA: none104.193.228.0/22No ROA covers it. Add a ROA for AS40193, maxLength 22.663 of 673
Route object: RIR104.193.228.0/22Route object only in ALTDB. Add it in the RIR database for the space.663 of 673
ROA: none104.244.56.0/21No ROA covers it. Add a ROA for AS40193, maxLength 21.663 of 673
Route object: RIR104.244.56.0/21Route object only in ALTDB. Add it in the RIR database for the space.663 of 673
ROA: none208.75.88.0/22No ROA covers it. Add a ROA for AS40193, maxLength 22.663 of 673
Route object: RIR208.75.88.0/22Route object only in ALTDB. Add it in the RIR database for the space.663 of 673
ROA: none208.90.32.0/21No ROA covers it. Add a ROA for AS40193, maxLength 21.663 of 673
Route object: RIR208.90.32.0/21Route object only in ALTDB. Add it in the RIR database for the space.663 of 673
ROA: none209.159.128.0/20No ROA covers it. Add a ROA for AS40193, maxLength 20.663 of 673
Route object: RIR209.159.128.0/20Route object only in ALTDB. Add it in the RIR database for the space.663 of 673
ROA: none2610:1a0::/32No ROA covers it. Add a ROA for AS40193, maxLength 32.631 of 636
Route object: RIR2610:1a0::/32Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
ROA: none2610:1a0:70::/44No ROA covers it. Add a ROA for AS40193, maxLength 44.631 of 636
Route object: RIR2610:1a0:70::/44Route object only in ALTDB. Add it in the RIR database for the space.631 of 636
ROA: none2610:1a0:a0::/44No ROA covers it. Add a ROA for AS40193, maxLength 44.631 of 636
Route object: RIR2610:1a0:a0::/44Route object only in ALTDB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

104.193.229.0/24ALTDBNo ROA
104.244.59.0/24ALTDBNo ROA
104.244.62.0/23ALTDBNo ROA
104.244.62.0/24ALTDBNo ROA
208.75.88.0/23ALTDBNo ROA
208.75.89.0/24ALTDBNo ROA
208.75.90.0/24ALTDBNo ROA
208.75.91.0/24ALTDBNo ROA
208.90.32.0/22ALTDBNo ROA
208.90.34.0/24ALTDBNo ROA
208.90.35.0/24ALTDBNo ROA
209.159.128.0/21ALTDBNo ROA
209.159.136.0/22ALTDBNo ROA
209.159.142.0/23ALTDBNo ROA
209.159.142.0/24ALTDBNo ROA
2610:1a0::/35ALTDBNo ROA
2610:1a0:6::/48ALTDBNo ROA
2610:1a0:60::/44ALTDBNo ROA
2610:1a0:ae::/48ALTDBNo ROA
2610:1a0:da::/48ALTDBNo ROA
2610:1a0:102::/48ALTDBNo ROA
2610:1a0:300::/48ALTDBNo ROA
2610:1a0:6000::/36ALTDBNo 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.