bgpreport

Network · data from 2026-11-12

AS202734 Tianshome

Registry name: Tianshome Junqi Tian, CA · PeeringDB

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

Announced routes

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

2a14:67c3:770::/44 No ROA Other IRR onlyRADB 631 99% 68
2a0f:1cc5:ffff::/48 No ROA RIR databaseRIPE 5 1%low visibility 6
23.158.20.0/24 Valid RIR databaseARIN, RADB 668 99% 66
2602:f92a:a440::/44 Valid RIR databaseARIN, RADB 635 100% 68
2001:678:1184::/48 Valid RIR databaseRADB, RIPE 632 99% 68
2a12:cb47:ffff::/48 Valid RIR databaseRIPE 33 5%low visibility 22

AS-SET

PeeringDB's irr_as_set for AS202734: RIPE::AS202734:AS-TIANSHOME. 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 (AS202734 isn't in the set, or no route object for AS202734 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 objectsAS202734 in itNot covered
RIPE::AS202734:AS-TIANSHOME RIPE 4114 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 4 are in fix.csv.

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a14:67c3:770::/44No ROA covers it. Add a ROA for AS202734, maxLength 44.631 of 636
Route object: RIR2a14:67c3:770::/44Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2a0f:1cc5:ffff::/48No ROA covers it. Add a ROA for AS202734, maxLength 48.5 of 636

Route objects not announced

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

2a0f:1cc5:1200::/40RADBValid

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.