bgpreport

Network · data from 2026-11-12

AS18973 TAG-ONLINE - TAG Online Inc.

Registry name: TAG-ONLINE - TAG Online Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18973, 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.
198.138.68.0/23 Valid Other IRR onlyRADB 672 100% 67
198.138.68.0/24 Valid Other IRR onlyRADB 672 100% 67
198.138.69.0/24 Valid Other IRR onlyRADB 672 100% 67
207.111.76.0/22 Valid Other IRR onlyRADB 672 100% 67
2606:1a00:1000::/36 Valid Other IRR onlyRADB 634 100% 67
2606:1a00:2000::/36 Valid Other IRR onlyRADB 634 100% 69
2606:1a00::/32 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

AS18973 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: RIR6
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: RIR198.138.68.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.138.68.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.138.69.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR207.111.76.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2606:1a00:1000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2606:1a00:2000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

198.138.68.0/27RADBValid
198.138.68.40/29RADBValid
198.138.68.48/29RADBValid
198.138.68.56/29RADBValid
198.138.68.80/29RADBValid
198.138.68.136/29RADBValid
198.138.68.144/28RADBValid
198.138.68.160/28RADBValid
198.138.69.16/29RADBValid
207.111.76.0/24RADBValid
207.111.77.0/27RADBValid
207.111.78.0/24RADBValid
207.111.79.0/27RADBValid
207.111.79.32/27RADBValid

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.