bgpreport

Network · data from 2026-11-12

AS18519 MTC Technologies

Registry name: MEDIAPOLIS-TELEPHONE-COMPANY - MTC Technologies, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18519, 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.
38.137.224.0/21 No ROA Other IRR onlyRADB 2 0%low visibility 2
72.251.192.0/20 Valid RIR databaseARIN, RADB 671 100% 68
167.254.244.0/22 Valid RIR databaseARIN, RADB 671 100% 68
172.81.16.0/22 Valid RIR databaseARIN, RADB 671 100% 68
2605:fac0::/32 Valid RIR databaseARIN, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS18519: ARIN::AS18519:AS-MTCTECH. 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 (AS18519 isn't in the set, or no route object for AS18519 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 objectsAS18519 in itNot covered
ARIN::AS18519:AS-MTCTECH ARIN 115 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.137.224.0/21No ROA covers it. Add a ROA for AS18519, maxLength 21.2 of 673
Route object: RIR38.137.224.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS18519 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.