bgpreport

Network · data from 2026-11-12

AS11983 TikTok U.S. Data Security

Registry name: TIKTOK-USDS - Tiktok U.S. Data Security Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11983, 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.
2602:f477:fe::/48 Valid Nonecovered by 2602:f477::/40 602 95% 67
71.18.40.0/24 Valid RIR databaseARIN 672 100% 67
71.18.191.0/24 Valid RIR databaseARIN 672 100% 67
71.18.192.0/24 Valid RIR databaseARIN 672 100% 67
71.18.193.0/24 Valid RIR databaseARIN 672 100% 67
71.18.31.0/24 Valid RIR databaseARIN 639 95% 67
71.18.130.0/24 Valid RIR databaseARIN 639 95% 67
71.18.166.0/24 Valid RIR databaseARIN 639 95% 67
147.160.180.0/24 Valid RIR databaseARIN 639 95% 67
2605:340:f0d7::/48 Valid RIR databaseARIN 635 100% 68
71.18.206.0/24 Valid RIR databaseARIN 628 93% 67
71.18.207.0/24 Valid RIR databaseARIN 628 93% 67
71.18.208.0/24 Valid RIR databaseARIN 628 93% 67
2605:340:f0d9::/48 Valid RIR databaseARIN 532 84% 66
2605:340:f03a::/48 Valid RIR databaseARIN 514 81% 68
2605:340:f087::/48 Valid RIR databaseARIN 506 80% 68
2605:340:f0cd::/48 Valid RIR databaseARIN 501 79% 67
2605:340:f097::/48 Valid RIR databaseARIN 498 78% 68
2605:340:f0b2::/48 Valid RIR databaseARIN 498 78% 68
2605:340:f0b6::/48 Valid RIR databaseARIN 498 78% 65
2605:340:f01e::/48 Valid RIR databaseARIN 490 77% 68
2605:340:f094::/48 Valid RIR databaseARIN 488 77% 65
2605:340:f0ac::/48 Valid RIR databaseARIN 487 77% 65
71.18.229.0/24 Valid RIR databaseARIN 483 72% 67
2605:340:f099::/48 Valid RIR databaseARIN 481 76% 65
71.18.224.0/24 Valid RIR databaseARIN 479 71% 66
71.18.60.0/24 Valid RIR databaseARIN 478 71% 66
147.160.177.0/24 Valid RIR databaseARIN 473 70% 66
71.18.11.0/24 Valid RIR databaseARIN 472 70% 66
71.18.162.0/24 Valid RIR databaseARIN 470 70% 66
71.18.183.0/24 Valid RIR databaseARIN 470 70% 66
71.18.38.0/24 Valid RIR databaseARIN 469 70% 66
71.18.10.0/24 Valid RIR databaseARIN 468 70% 66
71.18.125.0/24 Valid RIR databaseARIN 466 69% 65
71.18.43.0/24 Valid RIR databaseARIN 458 68% 66
71.18.52.0/24 Valid RIR databaseARIN 457 68% 65
71.18.53.0/24 Valid RIR databaseARIN 457 68% 65
71.18.116.0/24 Valid RIR databaseARIN 453 67% 66
71.18.243.0/24 Valid RIR databaseARIN 452 67% 66
71.18.33.0/24 Valid RIR databaseARIN 450 67% 66
71.18.8.0/24 Valid RIR databaseARIN 447 66% 66
71.18.95.0/24 Valid RIR databaseARIN 447 66% 66
71.18.50.0/24 Valid RIR databaseARIN 434 64% 64
71.18.104.0/24 Valid RIR databaseARIN 426 63% 64
192.64.15.0/24 Valid RIR databaseARIN 422 63% 64
71.18.188.0/24 Valid RIR databaseARIN 410 61% 65
71.18.123.0/24 Valid RIR databaseARIN 408 61% 65
71.18.124.0/24 Valid RIR databaseARIN 407 60% 65
2605:340:f033::/48 Valid RIR databaseARIN 402 63% 65
71.18.6.0/24 Valid RIR databaseARIN 393 58% 64
71.18.135.0/24 Valid RIR databaseARIN 393 58% 64
2605:340:f0a6::/48 Valid RIR databaseARIN 392 62% 65
147.160.182.0/24 Valid RIR databaseARIN 391 58% 64
2605:340:f080::/48 Valid RIR databaseARIN 343 54% 65
2605:340:f0ab::/48 Valid RIR databaseARIN 315 50% 64
2605:340:f0be::/48 Valid RIR databaseARIN 306 48% 64

AS-SET

PeeringDB's irr_as_set for AS11983: ARIN::AS-TUDS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS11983 isn't in the set, or no route object for AS11983 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS11983 in itNot covered
ARIN::AS-TUDS ARIN 1163 Yes 0

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

  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2602:f477:fe::/48No route object for it. A route object for 2602:f477::/40 with origin AS11983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11983 in the RIR database for the space.602 of 636

Route objects not announced

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

71.18.9.0/24ARINValid
71.18.61.0/24ARINValid
71.18.145.0/24ARINValid
152.235.0.0/17ARINValid
2602:f477::/40ARINValid
2605:340:f082::/48ARINValid
2605:340:f093::/48ARINValid
2605:340:f0c1::/48ARINValid

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.