bgpreport

Network · data from 2026-11-12

AS27613 TYLERTECH-CCS1 - Tyler Technologies, Inc.

Registry name: TYLERTECH-CCS1 - Tyler Technologies, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27613, 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.
207.245.148.0/24 Valid Other IRR onlyRADB 673 100% 68
2607:4060:3::/48 Valid Other IRR onlyRADB 636 100% 69
2607:4060:4::/48 Valid Other IRR onlyRADB 636 100% 69
2607:4060::/48 Valid Other IRR onlyRADB 635 100% 68
2607:4060:1::/48 Valid Other IRR onlyRADB 635 100% 68
2607:4060:2::/48 Valid Other IRR onlyRADB 635 100% 68
207.245.144.0/24 Valid RIR databaseARIN, RADB 673 100% 68
207.245.145.0/24 Valid RIR databaseARIN, RADB 673 100% 68
207.245.146.0/24 Valid RIR databaseARIN, RADB 673 100% 69
207.245.147.0/24 Valid RIR databaseARIN, RADB 673 100% 69

AS-SET

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

  • Route object: RIR6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR207.245.148.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2607:4060:3::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2607:4060:4::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2607:4060::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:4060:1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:4060:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

207.245.136.0/21ARINValid
207.245.148.0/22ARINValid
207.245.152.0/21ARINValid
208.64.232.0/21ARINValid
2607:4060::/36ARINValid

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.