bgpreport

Network · data from 2026-11-12

AS396259 TERIDION1 - Teridion inc

Registry name: TERIDION1 - Teridion inc, US · not in PeeringDB

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

Announced routes

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

136.228.20.0/24 Valid Other origin onlycovered by 136.228.0.0/19 672 100% 67
136.228.1.3/32 Valid Nonecovered by 136.228.1.0/24 1 0%low visibility 1
136.228.1.4/32 Valid Nonecovered by 136.228.1.0/24 1 0%low visibility 1
136.228.1.6/32 Valid Nonecovered by 136.228.1.0/24 1 0%low visibility 1
136.228.1.10/32 Valid Nonecovered by 136.228.1.0/24 1 0%low visibility 1
136.228.1.14/32 Valid Nonecovered by 136.228.1.0/24 1 0%low visibility 1
136.228.26.0/24 Valid Other IRR onlyRADB 673 100% 66
136.228.28.0/24 Valid Other IRR onlyRADB 673 100% 66
139.60.205.0/24 Valid Other IRR onlyRADB 673 100% 67
136.228.21.0/24 Valid Other IRR onlyRADB 672 100% 67
139.60.200.0/24 Valid Other IRR onlyRADB 672 100% 67
139.60.207.0/24 Valid Other IRR onlyRADB 672 100% 67
136.228.27.0/24 Valid Other IRR onlyRADB 669 99% 67
136.228.0.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.2.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.3.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.5.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.6.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.7.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.8.0/24 Valid RIR databaseARIN, RADB 673 100% 66
136.228.9.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.11.0/24 Valid RIR databaseARIN, RADB 673 100% 67
136.228.4.0/24 Valid RIR databaseARIN, RADB 672 100% 67
136.228.10.0/24 Valid RIR databaseARIN, RADB 672 100% 67
136.228.12.0/24 Valid RIR databaseARIN, RADB 672 100% 67
136.228.14.0/24 Valid RIR databaseARIN, RADB 672 100% 67
136.228.1.0/24 Valid RIR databaseARIN, RADB 671 100% 67
136.228.13.0/24 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

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

  • Route object: none6
  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none136.228.20.0/24Route objects for it name AS9116, AS12400, AS12849. A route object for 136.228.0.0/19 with origin AS396259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396259 in the RIR database for the space.672 of 673
Route object: none136.228.1.3/32No route object for it. A route object for 136.228.1.0/24 with origin AS396259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS396259 in the RIR database for the space.1 of 673
Route object: none136.228.1.4/32No route object for it. A route object for 136.228.1.0/24 with origin AS396259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS396259 in the RIR database for the space.1 of 673
Route object: none136.228.1.6/32No route object for it. A route object for 136.228.1.0/24 with origin AS396259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS396259 in the RIR database for the space.1 of 673
Route object: none136.228.1.10/32No route object for it. A route object for 136.228.1.0/24 with origin AS396259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS396259 in the RIR database for the space.1 of 673
Route object: none136.228.1.14/32No route object for it. A route object for 136.228.1.0/24 with origin AS396259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS396259 in the RIR database for the space.1 of 673
Route object: RIR136.228.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR136.228.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR139.60.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR136.228.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.60.200.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.60.207.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR136.228.27.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

136.228.0.0/19ARINValid
136.228.15.0/24RADBValid
136.228.16.0/24RADBValid
136.228.19.0/24RADBValid
136.228.29.0/24RADBValid
136.228.31.0/24ARINValid
139.60.200.0/21ARINValid

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.