bgpreport

Network · data from 2026-11-12

AS27644 THREATSTOP - ThreatSTOP

Registry name: THREATSTOP - ThreatSTOP, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27644, 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:11e:f000::/44 No ROA Other IRR onlyRADB 636 100% 70
2620:11e:f005::/48 No ROA Other IRR onlyRADB 636 100% 70
2620:11e:f006::/48 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70

AS-SET

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

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2620:11e:f000::/44No ROA covers it. Add a ROA for AS27644, maxLength 44.636 of 636
Route object: RIR2620:11e:f000::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:11e:f005::/48No ROA covers it. Add a ROA for AS27644, maxLength 48.636 of 636
Route object: RIR2620:11e:f005::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:11e:f006::/48No ROA covers it. Add a ROA for AS27644, maxLength 48.636 of 636
Route object: RIR2620:11e:f006::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

67.207.213.0/24RADBNo ROA
192.124.129.0/24NTTCOM, RADBValid
207.167.126.0/23RADBNo ROA
2620:11e:f004::/48RADBNo ROA
2620:11e:f007::/48RADBNo 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.