bgpreport

Network · data from 2026-11-12

AS13911 TERA-BYTE - Tera-byte Dot Com Inc.

Registry name: TERA-BYTE - Tera-byte Dot Com Inc., CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13911, 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.
216.194.76.0/22 Invalid: origin Other origin onlycovered by 216.194.64.0/20 1 0%low visibility 1
52.124.8.0/21 No ROA Other IRR onlyALTDB, RADB 673 100% 67
142.202.32.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 67
199.96.208.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 67
199.217.120.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 67
204.209.56.0/23 No ROA Other IRR onlyALTDB, RADB 671 100% 67
209.142.108.0/22 No ROA Other IRR onlyRADB 671 100% 67
206.75.90.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
216.194.64.0/21 Valid RIR databaseALTDB, ARIN 673 100% 67
216.234.160.0/21 Valid RIR databaseALTDB, ARIN 673 100% 67
66.51.108.0/22 Valid RIR databaseALTDB, ARIN 671 100% 67
198.161.206.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none6
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin216.194.76.0/22ROAs covering it name AS60503, not AS13911. If AS13911 should announce it, add a ROA for AS13911.1 of 673
Route object: none216.194.76.0/22Route objects for it name AS60503. A route object for 216.194.64.0/20 with origin AS13911 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13911 in the RIR database for the space.1 of 673
ROA: none52.124.8.0/21No ROA covers it. Add a ROA for AS13911, maxLength 21.673 of 673
Route object: RIR52.124.8.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none142.202.32.0/22No ROA covers it. Add a ROA for AS13911, maxLength 22.671 of 673
Route object: RIR142.202.32.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.96.208.0/22No ROA covers it. Add a ROA for AS13911, maxLength 22.671 of 673
Route object: RIR199.96.208.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.217.120.0/22No ROA covers it. Add a ROA for AS13911, maxLength 22.671 of 673
Route object: RIR199.217.120.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.209.56.0/23No ROA covers it. Add a ROA for AS13911, maxLength 23.671 of 673
Route object: RIR204.209.56.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none209.142.108.0/22No ROA covers it. Add a ROA for AS13911, maxLength 22.671 of 673
Route object: RIR209.142.108.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR206.75.90.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.181.208.0/20RADBNo ROA
67.211.64.0/20RADBNo ROA
142.202.35.0/24ARINValid
204.209.20.0/24RADBNo ROA
216.194.64.0/19RADBNo ROA
216.194.64.0/20RADBNo ROA
2610:78::/32ALTDBNo 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.