bgpreport

Network · data from 2026-11-12

AS10700 TECINFO

Registry name: TECINFO - TECINFO, Inc., US · PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS10700, seen from no peer

Announced routes

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

216.220.128.0/19 No ROA Other IRR onlyRADB 670 100% 68
2605:80c0::/32 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS10700: RADB::AS-TECINFO. 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 (AS10700 isn't in the set, or no route object for AS10700 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 objectsAS10700 in itNot covered
RADB::AS-TECINFO RADB 119 No 2

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

  • ROA: none2
  • Route object: RIR2
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none216.220.128.0/19No ROA covers it. Add a ROA for AS10700, maxLength 19.670 of 673
Route object: RIR216.220.128.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2605:80c0::/32No ROA covers it. Add a ROA for AS10700, maxLength 32.635 of 636
Route object: RIR2605:80c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: own ASNRADB::AS-TECINFOAS10700 isn't in AS-TECINFO (RADB) once expanded. Add AS10700 to it.

Route objects not announced

Every route object with origin AS10700 is announced.

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.