bgpreport

Network · data from 2026-11-12

AS267035 MS TELECOM

Registry name: AS267035 - MS TELECOM LTDA ME, BR · PeeringDB

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

Announced routes

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

45.227.148.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.227.149.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.227.148.0/23 No ROA Other IRR onlyRADB 669 99% 67
45.227.150.0/24 No ROA Other IRR onlyRADB 668 99% 67
45.227.151.0/24 No ROA Other IRR onlyRADB 668 99% 67
2804:4728::/32 No ROA Other IRR onlyRADB 636 100% 69
2804:4728::/33 No ROA Other IRR onlyRADB 636 100% 69
2804:4728:8000::/33 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS267035: AS267035:AS-CONE. 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 (AS267035 isn't in the set, or no route object for AS267035 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 objectsAS267035 in itNot covered
AS267035:AS-CONE RADB 4012,640 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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.227.148.0/24No ROA covers it. Add a ROA for AS267035, maxLength 24.670 of 673
Route object: RIR45.227.148.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.227.149.0/24No ROA covers it. Add a ROA for AS267035, maxLength 24.670 of 673
Route object: RIR45.227.149.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.227.148.0/23No ROA covers it. Add a ROA for AS267035, maxLength 23.669 of 673
Route object: RIR45.227.148.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.227.150.0/24No ROA covers it. Add a ROA for AS267035, maxLength 24.668 of 673
Route object: RIR45.227.150.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.227.151.0/24No ROA covers it. Add a ROA for AS267035, maxLength 24.668 of 673
Route object: RIR45.227.151.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:4728::/32No ROA covers it. Add a ROA for AS267035, maxLength 32.636 of 636
Route object: RIR2804:4728::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:4728::/33No ROA covers it. Add a ROA for AS267035, maxLength 33.636 of 636
Route object: RIR2804:4728::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:4728:8000::/33No ROA covers it. Add a ROA for AS267035, maxLength 33.636 of 636
Route object: RIR2804:4728:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.227.148.0/22RADBNo ROA
45.227.150.0/23RADBNo 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.