bgpreport

Network · data from 2026-11-12

AS270237 MULT3 TELECOM

Registry name: AS270237 - Mult3 Telecom, BR · PeeringDB

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

Announced routes

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

2804:68ec:8000::/34 No ROA Nonecovered by 2804:68ec:8000::/33 631 99% 67
45.189.165.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
45.189.164.0/24 No ROA Other IRR onlyRADB, TC 669 99% 66
45.189.166.0/24 No ROA Other IRR onlyRADB, TC 669 99% 66
45.189.167.0/24 No ROA Other IRR onlyRADB, TC 669 99% 66
2804:68ec::/32 No ROA Other IRR onlyRADB, TC 630 99% 67
2804:68ec::/33 No ROA Other IRR onlyTC 346 54% 64
45.189.164.0/23 No ROA Other IRR onlyRADB, TC 193 29% 54
45.189.166.0/23 No ROA Other IRR onlyRADB, TC 193 29% 54
45.189.164.0/22 No ROA Other IRR onlyRADB, TC 136 20% 49

AS-SET

PeeringDB's irr_as_set for AS270237: AS270237:AS-ANNOUNCEMENTS. 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 (AS270237 isn't in the set, or no route object for AS270237 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 objectsAS270237 in itNot covered
AS270237:AS-ANNOUNCEMENTS TC 1210 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 21 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:68ec:8000::/34No ROA covers it. Add a ROA for AS270237, maxLength 34.631 of 636
Route object: none2804:68ec:8000::/34No route object for it. A route object for 2804:68ec:8000::/33 with origin AS270237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270237 in the RIR database for the space.631 of 636
ROA: none45.189.165.0/24No ROA covers it. Add a ROA for AS270237, maxLength 24.671 of 673
Route object: RIR45.189.165.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.164.0/24No ROA covers it. Add a ROA for AS270237, maxLength 24.669 of 673
Route object: RIR45.189.164.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none45.189.166.0/24No ROA covers it. Add a ROA for AS270237, maxLength 24.669 of 673
Route object: RIR45.189.166.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none45.189.167.0/24No ROA covers it. Add a ROA for AS270237, maxLength 24.669 of 673
Route object: RIR45.189.167.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:68ec::/32No ROA covers it. Add a ROA for AS270237, maxLength 32.630 of 636
Route object: RIR2804:68ec::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:68ec::/33No ROA covers it. Add a ROA for AS270237, maxLength 33.346 of 636
Route object: RIR2804:68ec::/33Route object only in TC. Add it in the RIR database for the space.346 of 636
ROA: none45.189.164.0/23No ROA covers it. Add a ROA for AS270237, maxLength 23.193 of 673
Route object: RIR45.189.164.0/23Route object only in RADB, TC. Add it in the RIR database for the space.193 of 673
ROA: none45.189.166.0/23No ROA covers it. Add a ROA for AS270237, maxLength 23.193 of 673
Route object: RIR45.189.166.0/23Route object only in RADB, TC. Add it in the RIR database for the space.193 of 673
ROA: none45.189.164.0/22No ROA covers it. Add a ROA for AS270237, maxLength 22.136 of 673
Route object: RIR45.189.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.136 of 673

Route objects not announced

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

2804:68ec:8000::/33TCNo ROA

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.