bgpreport

Network · data from 2026-11-12

AS7181 Tierpoint 7181

Registry name: AS-TIERP-7181 - TierPoint, LLC, US · PeeringDB

1IPv4 routes 100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
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
12Route objects not announced registered with origin AS7181, seen from no peer

Announced routes

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

209.59.31.0/24 Valid None 363 54% 57

AS-SET

PeeringDB's irr_as_set for AS7181: RADB::AS-TP7181. 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 (AS7181 isn't in the set, or no route object for AS7181 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 objectsAS7181 in itNot covered
RADB::AS-TP7181 RADB1 member set in no database: AS-CRUNCHBITS 321166,540 Yes 1

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

  • Route object: none1
  • AS-SET: missing member1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none209.59.31.0/24No route object for it. Add a route object with origin AS7181 in the RIR database for the space.363 of 673
AS-SET: missing memberRADB::AS-TP7181AS-TP7181 (RADB) lists AS-CRUNCHBITS; no IRR database read has it.

Route objects not announced

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

72.249.112.0/24RADBValid
2001:19b8::/32ARINValid
2001:4970::/32ARINValid
2600:2c00::/30ARINValid
2604:7e00::/32ARINValid
2604:7f80::/32ARINValid
2606:a700::/32ARINValid
2607:f1d0::/32ARINValid
2607:f3f8::/32ARINValid
2607:fc38::/32ARINValid
2607:fdb8::/32ARINValid
2607:fdb8:4::/48RADBValid

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.