Network · data from 2026-11-12
AS26714 NORTHEAST-TEXAS-COMMUNITY-COLLEGE - Northeast Texas Community College
Registry name: NORTHEAST-TEXAS-COMMUNITY-COLLEGE - Northeast Texas Community College, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26714, 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.
| 68.69.50.0/24 | Valid | None | 671 100% |
| 75.108.201.0/24 | Valid | None | 671 100% |
AS-SET
AS26714 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 4 are in fix.csv.
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 68.69.50.0/24 | No route object for it. Add a route object with origin AS26714 in the RIR database for the space. |
| Route object: none | 75.108.201.0/24 | No route object for it. Add a route object with origin AS26714 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26714 whose prefix no peer sees AS26714 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.124.3.0/24 | RADB | No ROA |
| 2620:104:b000::/48 | RADB | No 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.